autopilot_status

Get exploration status. If explorationId is provided, shows details. Otherwise lists all explorations.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/autopilot-status.md

WHAT IT DOES

What autopilot_status does on Claude Mobile

AI agents call autopilot_status to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why autopilot_status is rated Low

This tool queries the status of explorations and returns information about them. It performs no mutations, side effects, or irreversible operations. The 'explorationId' parameter allows filtering the query results, but fundamentally this is a read/retrieval operation. Even in the context of mobile device automation, checking status is a benign information retrieval action with no blast radius.

From the tool's definition 'Get exploration status' with conditional display of details or list all explorations—retrieves information without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs autopilot_status 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_status, this is the rule to start with:

autopilot_status Allowed

autopilot_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "autopilot_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every autopilot_status call is checked against it from then on.

FAQ

Questions about autopilot_status

What does the autopilot_status tool do? +

Get exploration status. If explorationId is provided, shows details. Otherwise lists all explorations. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on autopilot_status? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for autopilot_status: 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.

What risk level is autopilot_status? +

autopilot_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit autopilot_status? +

Yes. Add a rate_limit block to the autopilot_status 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.

How do I block autopilot_status completely? +

Set action: deny in the PolicyLayer policy for autopilot_status. 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.

What MCP server provides autopilot_status? +

autopilot_status 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.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →