autopilot_tests

List or get generated test scenarios for an exploration.

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-tests.md

WHAT IT DOES

What autopilot_tests does on Claude Mobile

AI agents call autopilot_tests 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_tests is rated Low

The tool retrieves or queries test scenario data. The verbs 'list' and 'get' indicate data retrieval only. There is no indication of test execution (which would be Execute), creation of new tests (Write), or deletion of tests (Destructive). The blast radius of misuse is minimal since reading test scenarios cannot change system state or trigger unintended actions on the device.

From the tool's definition Tool description states 'List or get generated test scenarios' — these are read-only operations that retrieve pre-existing test data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

autopilot_tests Allowed

autopilot_tests 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_tests": {}
  }
}

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_tests call is checked against it from then on.

FAQ

Questions about autopilot_tests

What does the autopilot_tests tool do? +

List or get generated test scenarios for an exploration. 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_tests? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for autopilot_tests: 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_tests? +

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

Can I rate-limit autopilot_tests? +

Yes. Add a rate_limit block to the autopilot_tests 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_tests completely? +

Set action: deny in the PolicyLayer policy for autopilot_tests. 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_tests? +

autopilot_tests 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

The MCP Attack Database →

Guides

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