sim_shutdown

THE RISK

Critical Risk

Why sim_shutdown needs a policy

Shutting down a simulator is an irreversible action that terminates running processes and can disrupt ongoing work. Passing udid='booted' to stop ALL running simulators simultaneously amplifies the blast radius significantly, potentially killing multiple active sessions/environments at once with no undo capability.

From the tool's definition "Shut down a simulator. Pass udid='booted' to stop all running ones."

Documented attack patterns abuse exactly the kind of access sim_shutdown gives an agent:

POLICY

How to control sim_shutdown

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sim_shutdown:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "sim_shutdown"
  ]
}

sim_shutdown disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Claude Pascal MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude Pascal MCP Server tools

Destructive paserver_remove paserver_remove Destructive sim_uninstall Uninstall an app from a simulator. Destructive sim_terminate Terminate a running app by bundle identifier. Execute adb_launch_app adb_launch_app Execute adb_stop_app Force-stop an app on the Android device. Execute build_dproj build_dproj Execute compile_delphi_project compile_delphi_project Execute compile_pascal compile_pascal

All 53 Claude Pascal MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Claude Pascal MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sim_shutdown

What does the sim_shutdown tool do? +

Shut down a simulator. Pass udid='booted' to stop all running ones. It is categorised as a Destructive tool in the Claude Pascal MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sim_shutdown? +

Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for sim_shutdown: 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 Pascal MCP Server. Nothing to install.

What risk level is sim_shutdown? +

sim_shutdown is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sim_shutdown? +

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

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

sim_shutdown is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Pascal MCP Server tool call.

Start from Claude Pascal MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →