AI agents invoke pod_update to trigger actions in Xcode. 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.
Running 'pod update' executes an external shell command that modifies the project's dependency graph, Podfile.lock, and Pods directory. It triggers network requests, resolves new dependency versions, and modifies project files. This is an Execute-level action due to running external operations; it also has Write side effects, but Execute is the more severe applicable category.
From the tool's definition Tool name 'pod_update' and server description 'Runs' (truncated) — 'pod update' is a CocoaPods command that executes an external CLI process to resolve, fetch, and integrate pod dependencies into an Xcode project
Documented attack patterns abuse exactly the kind of access pod_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"pod_update": {
"limits": [
{
"counter": "pod_update_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pod_update 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.
Free to start. No card required.
Runs. It is categorised as a Execute tool in the Xcode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xcode MCP server in PolicyLayer and add a rule for pod_update: 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.
pod_update 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 pod_update 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 pod_update. 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.
pod_update 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.
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.