Security and help

Understand data handling and resolve common issues.

Authentication

Sign-in is browser-based; tokens are held by your MCP client, not the model. Access mirrors your Mozark role and permissions.

What leaves your workspace

When the assistant uses a tool, the tool's result (a test case, a device list, a screenshot) is sent to the AI model so it can respond. Large binaries never do: app uploads stream directly from your machine to Mozark's file store, and step-evidence screenshots are captured and attached server-side.

Credentials in commands

appium_get_app_upload_command returns a curl command with a live bearer token baked in so an agent can run it unattended. Treat it like a password — run it, don't paste it into chat logs, tickets or version control.

Writes and deletes

The assistant only writes on explicit instruction and confirms before bulk deletes or plan changes. Deletes are soft deletes.

Session hygiene

Device sessions are released automatically at the end of a task unless you ask to keep one open. Open sessions consume device time and block other users.

Questions

Contact your Mozark administrator or Mozark support for data-residency, retention and compliance details.