> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/mcp/mozark-mcp-docs/security-and-help.md). # 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 {% hint style="warning" %} `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. {% endhint %} ## 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mozark.ai/mcp/mozark-mcp-docs/security-and-help.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.