recorder_play

Replay a saved scenario. Executes all steps sequentially with optional speed/timeout control.

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What recorder_play does on Claude Mobile

AI agents invoke recorder_play 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.

RISK

Why recorder_play is rated High

This tool executes a pre-recorded sequence of UI interactions and device operations. Since it can replay arbitrary automation steps (which may include app installs, text input, UI interactions, or other operations), it falls under Execute.

From the tool's definition 'Replay a saved scenario. Executes all steps sequentially' - the tool runs a sequence of recorded actions on a mobile device

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_play Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recorder_play": {
      "limits": [
        {
          "counter": "recorder_play_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about recorder_play

What does the recorder_play tool do? +

Replay a saved scenario. Executes all steps sequentially with optional speed/timeout control. 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.

How do I enforce a policy on recorder_play? +

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

recorder_play is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit recorder_play? +

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

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

recorder_play 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 → High-risk tools on this server →

Across the catalogue

music_play on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →