recorder_add_step
Manually add a step to the active recording
This record as markdown: /tools/alexgladkov-claude-in-mobile/recorder-add-step.md
What recorder_add_step does on Claude Mobile
AI agents use recorder_add_step to create or update resources in Claude Mobile, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mobile environment.
Why recorder_add_step is rated Medium
The tool creates or appends data to a recording artifact. While recordings are used to automate mobile device interactions, adding a step is metadata manipulation rather than direct device control. The effect is reversible (steps can be edited or removed), distinguishing it from destructive operations.
From the tool's definition Tool description states 'Manually add a step to the active recording' — this modifies the state of an active recording by inserting new content, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs recorder_add_step 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_add_step, this is the rule to start with:
recorder_add_step stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 recorder_add_step call is checked against it from then on.
Questions about recorder_add_step
Manually add a step to the active recording. It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for recorder_add_step: 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.
recorder_add_step is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the recorder_add_step 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 recorder_add_step. 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.
recorder_add_step 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.
This server
Across the catalogue