autopilot
AI Test Autopilot. explore: auto-navigate app and build navigation graph. generate: create test scenarios from exploration. heal: self-heal broken test selectors. status: exploration status. tests: list/get generated tests.
This record as markdown: /tools/alexgladkov-claude-in-mobile/autopilot.md
What autopilot does on Claude Mobile
AI agents invoke autopilot to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why autopilot is rated High
This is an Execute category tool because it runs automated sequences that trigger external operations on the mobile device (app navigation, UI interactions, test execution). While individual operations like reading state might be Read-level, the autopilot's core function is to automatically execute navigation and test scenarios whose side effects (app state changes, data modifications) depend on generated test logic.
From the tool's definition The tool performs 'auto-navigate app', 'create test scenarios', 'self-heal broken test selectors', and 'exploration status' operations.
Attacks that exploit this kind of access
The rule that runs autopilot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For autopilot, this is the rule to start with:
autopilot stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every autopilot call is checked against it from then on.
Questions about autopilot
AI Test Autopilot. explore: auto-navigate app and build navigation graph. generate: create test scenarios from exploration. heal: self-heal broken test selectors. status: exploration status. tests: list/get generated tests. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for autopilot: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Mobile. Nothing to install.
autopilot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the autopilot rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for autopilot. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
autopilot is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue