recorder_start

Begin recording user interactions as a test scenario

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

WHAT IT DOES

What recorder_start does on Claude Mobile

AI agents invoke recorder_start 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_start is rated High

This tool triggers an external operation (recording mechanism) on a mobile device that has side effects—it initiates capture of user interactions and creates artifacts (recordings). While not destructive or financial, it is an Execute-category action because it activates a system-level process whose outcome depends on how the AI agent invokes it.

From the tool's definition Tool name 'recorder_start' and description 'Begin recording user interactions as a test scenario' indicate it initiates a recording operation that captures and logs device interactions, which is an external operation whose effects depend on arguments (device…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_start Rate-limited

recorder_start 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_start": {
      "limits": [
        {
          "counter": "recorder_start_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_start call is checked against it from then on.

FAQ

Questions about recorder_start

What does the recorder_start tool do? +

Begin recording user interactions as a test scenario. 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_start? +

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

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

Can I rate-limit recorder_start? +

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

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

recorder_start 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

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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