recorder_list

List saved test scenarios

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/alexgladkov-claude-in-mobile/recorder-list.md

WHAT IT DOES

What recorder_list does on Claude Mobile

AI agents call recorder_list to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why recorder_list is rated Low

This tool retrieves and displays a list of saved test scenarios from the mobile device automation system. It performs a simple query operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could only view what test scenarios exist, posing no risk to data integrity, device state, or operations.

From the tool's definition Tool name 'recorder_list' and description 'List saved test scenarios' indicate data retrieval with no modification or execution. The verb 'list' is a classic read operation that queries existing state without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recorder_list Allowed

recorder_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recorder_list": {}
  }
}

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

FAQ

Questions about recorder_list

What does the recorder_list tool do? +

List saved test scenarios. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recorder_list? +

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

recorder_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit recorder_list? +

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

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

recorder_list 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →