Moves a file or directory to a new location within allowed directories.
AI agents use move_file to create or update resources in Xcode — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xcode environment.
This tool modifies the state of the filesystem by relocating files/directories, which is a write operation. While the movement is reversible (files can be moved back), the operation could disrupt project structure or cause build failures if applied incorrectly. The restriction to 'allowed directories' provides some safety guardrails.
From the tool's definition Tool description states it 'Moves a file or directory to a new location within allowed directories.' Moving is a reversible modification operation that changes file/directory location but does not delete or execute code.
Documented attack patterns abuse exactly the kind of access move_file 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 move_file:
{
"version": "1",
"default": "deny",
"tools": {
"move_file": {
"limits": [
{
"counter": "move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Moves a file or directory to a new location within allowed directories. It is categorised as a Write tool in the Xcode MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xcode MCP server in PolicyLayer and add a rule for move_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.
move_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the move_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 move_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.
move_file 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.