Critical Risk →

pod_deintegrate

Deintegrate CocoaPods from the active project, removing all traces of CocoaPods.

How to control pod_deintegrate ↓

AI agents call pod_deintegrate to permanently remove resources in Xcode — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly removes CocoaPods integration from a project, deleting configuration, files, and references that cannot be automatically restored without re-integrating. 'Removing all traces' implies a comprehensive, potentially irreversible deletion of CocoaPods-managed dependencies and project modifications.

From the tool's definition Deintegrate CocoaPods from the active project, removing all traces of CocoaPods

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

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

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

pod_deintegrate 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 Xcode — 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.

Go deeper

What does the pod_deintegrate tool do? +

Deintegrate CocoaPods from the active project, removing all traces of CocoaPods. It is categorised as a Destructive tool in the Xcode 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 pod_deintegrate? +

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

What risk level is pod_deintegrate? +

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

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

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

pod_deintegrate is provided by the Xcode MCP server (xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xcode tool call.

Deterministic rules across all 69 Xcode tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

69 Xcode tools catalogued and risk-classified — across an index of 42,500+ 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.