system_shell
Execute a shell command on the device. SECURITY: shell metacharacters
This record as markdown: /tools/alexgladkov-claude-in-mobile/system-shell.md
What system_shell does on Claude Mobile
AI agents invoke system_shell 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.
Why system_shell is rated High
This tool allows execution of arbitrary shell commands on the target device, giving an AI agent the ability to run any command supported by the device's shell. While not inherently destructive (the agent could theoretically limit itself to safe commands), shell command execution is an Execute category risk: the effects depend entirely on the arguments provided, and a single malicious or misconfigured command can…
From the tool's definition Tool name 'system_shell' and description 'Execute a shell command on the device' with explicit mention of shell metacharacters handling. The tool directly executes arbitrary shell commands on a connected mobile device via ADB or simctl.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_shell 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 system_shell, this is the rule to start with:
system_shell 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every system_shell call is checked against it from then on.
Questions about system_shell
Execute a shell command on the device. SECURITY: shell metacharacters. 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.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for system_shell: 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.
system_shell is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the system_shell 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.
Set action: deny in the PolicyLayer policy for system_shell. 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.
system_shell 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.
More on Claude Mobile, and thousands of servers like it.
Across the catalogue