Remove a file from the Xcode project
AI agents call xcode_remove_file 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.
Removing a file from an Xcode project deletes data that cannot be easily recovered without version control intervention. This is a destructive operation with high blast radius if misused by an agent—it could remove critical source code, configuration files, or resources, breaking the build or losing work.
From the tool's definition Tool name 'xcode_remove_file' and description 'Remove a file from the Xcode project' indicate irreversible deletion of project files.
Attacks that exploit this kind of access
Remove a file from the Xcode project. 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.
Register the Xcode MCP server in PolicyLayer and add a rule for xcode_remove_file: 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.
xcode_remove_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the xcode_remove_file 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 xcode_remove_file. 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.
xcode_remove_file is provided by the Xcode MCP server (raunaksplanet/xcode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →