Critical Risk →

simulator_keychain

Manipulate the device keychain: add root certificates, add certificates, or reset the entire keychain.

Accepts file system path (path); Bulk/mass operation — affects multiple targets; Admin/system-level operation

Part of the Preflight Ios MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

preflight-ios-mcp Destructive

AI agents may call simulator_keychain to permanently remove or destroy resources in Preflight Ios. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call simulator_keychain in a loop, permanently destroying resources in Preflight Ios. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-ethanackerman-git-preflight-ios-mcp.yaml
tools:
  simulator_keychain:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Preflight Ios policy for all 82 tools.

Tool Name simulator_keychain
Category Destructive
Risk Level Critical

View all 82 tools →

Agents calling destructive-class tools like simulator_keychain have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

simulator_keychain is one of the critical-risk operations in Preflight Ios. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the simulator_keychain tool do? +

Manipulate the device keychain: add root certificates, add certificates, or reset the entire keychain.. It is categorised as a Destructive tool in the Preflight Ios 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 simulator_keychain? +

Add a rule in your Intercept YAML policy under the tools section for simulator_keychain. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Preflight Ios MCP server.

What risk level is simulator_keychain? +

simulator_keychain 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 simulator_keychain? +

Yes. Add a rate_limit block to the simulator_keychain rule in your Intercept 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 simulator_keychain completely? +

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

simulator_keychain is provided by the Preflight Ios MCP server (preflight-ios-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.