recorder_remove_step

Remove a step from the active recording by index

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-remove-step.md

WHAT IT DOES

What recorder_remove_step does on Claude Mobile

AI agents call recorder_remove_step 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_remove_step is rated Critical

Removing a step from a recording is an irreversible deletion of recorded data. Once a step is removed by index, it cannot be recovered without re-recording. This qualifies as Destructive. Severity is medium because it affects a recording session rather than production data or device state.

From the tool's definition Remove a step from the active recording by index

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_remove_step Hidden

recorder_remove_step 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_remove_step"
  ]
}

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

FAQ

Questions about recorder_remove_step

What does the recorder_remove_step tool do? +

Remove a step from the active recording by index. 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_remove_step? +

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

What risk level is recorder_remove_step? +

recorder_remove_step 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_remove_step? +

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

How do I block recorder_remove_step completely? +

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

What MCP server provides recorder_remove_step? +

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

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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →