recorder_stop

Stop recording and save scenario (or discard)

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Medium RISK CLASS

Category Write

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

WHAT IT DOES

What recorder_stop does on Claude Mobile

AI agents use recorder_stop 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.

RISK

Why recorder_stop is rated Medium

This tool stops a recording session and either saves or discards the recorded scenario. The primary action (saving a scenario) is a Write operation — it creates/persists data. The discard path is reversible in context (no data was saved). Since it doesn't execute commands, delete existing data irreversibly, or involve financial operations, Write is the most applicable category.

From the tool's definition Stop recording and save scenario (or discard)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_stop Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recorder_stop": {
      "limits": [
        {
          "counter": "recorder_stop_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about recorder_stop

What does the recorder_stop tool do? +

Stop recording and save scenario (or discard). 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.

How do I enforce a policy on recorder_stop? +

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

recorder_stop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit recorder_stop? +

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

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

recorder_stop 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

Govern customer-ops agents →Argument validation →Scoped token →