recorder

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What recorder does on Claude Mobile

AI agents call recorder to permanently remove resources in Claude Mobile, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why recorder is rated Critical

This tool spans multiple risk categories. 'delete: remove' and 'remove_step: delete step' are irreversible destructive operations on saved test data. 'play: replay' executes recorded UI automation sequences against a real Android/iOS device, which could trigger arbitrary device interactions depending on what was recorded — this is Execute-level at minimum.

From the tool's definition 'delete: remove' and 'play: replay' and 'export: convert format' — the tool can delete saved scenarios, replay test actions on a real device (Execute-level), and remove steps irreversibly

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder Hidden

recorder is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "recorder"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about recorder

What does the recorder tool do? +

Test scenario recorder. start: begin recording. stop: save scenario. status: check state. add_step: manual step. remove_step: delete step. list: saved scenarios. show: display scenario. delete: remove. play: replay. export: convert format. It is categorised as a Destructive tool in the Claude Mobile MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on recorder? +

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

recorder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit recorder? +

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

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

recorder 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →