Critical Risk →

sim_terminate

Terminate a running app by bundle identifier.

How to control sim_terminate ↓

What sim_terminate does on Claude Pascal MCP Server

AI agents call sim_terminate to permanently remove resources in Claude Pascal MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why sim_terminate needs a policy

Terminating a running application is an irreversible action in the moment — it forcibly kills the process, potentially causing data loss (unsaved state, in-progress operations). This cannot be undone once executed, making it Destructive. The blast radius is high because it could kill critical applications mid-operation, causing data corruption or service disruption.

From the tool's definition Terminate a running app by bundle identifier

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

How to control sim_terminate

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_terminate:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "sim_terminate"
  ]
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about sim_terminate

What does the sim_terminate tool do? +

Terminate a running app by bundle identifier. 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_terminate? +

Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for sim_terminate: 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_terminate? +

sim_terminate 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_terminate? +

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

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

sim_terminate 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.

Free to start. No card required.

53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.