recorder_export

Export scenario as flow_steps (for flow_run) or markdown checklist

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

WHAT IT DOES

What recorder_export does on Claude Mobile

AI agents use recorder_export 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_export is rated Medium

The tool creates or generates new data (flow_steps or markdown format) from existing scenario data. This is a Write operation because it produces new data artifacts that can be stored or used elsewhere. It does not delete anything (not Destructive), does not move money (not Financial), does not execute code/commands directly (not Execute—it merely exports recorded data), and is reversible.

From the tool's definition Tool exports/creates a new artifact (flow_steps or markdown checklist) from an existing scenario. Description uses 'export' which generates new data output.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_export Rate-limited

recorder_export 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_export": {
      "limits": [
        {
          "counter": "recorder_export_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_export call is checked against it from then on.

FAQ

Questions about recorder_export

What does the recorder_export tool do? +

Export scenario as flow_steps (for flow_run) or markdown checklist. 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_export? +

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

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

Can I rate-limit recorder_export? +

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

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

recorder_export 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 →