AI agents use copy_file to create or update resources in Apple Shortcuts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Shortcuts environment.
This tool performs a file copy operation, which creates or modifies data (new file at destination) but is reversible—the original remains and the copy can be deleted. This fits the Write category. Severity is medium because unintended copies could fill disk space or expose sensitive files to unintended locations, but the operation itself is not destructive and can be undone.
From the tool's definition The tool description explicitly states it 'Copy a file or folder to a new location.' Copying creates new data in a destination, which is a reversible write operation. The tool is part of an Apple Shortcuts automation server that executes macOS operations.
Documented attack patterns abuse exactly the kind of access copy_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_file:
{
"version": "1",
"default": "deny",
"tools": {
"copy_file": {
"limits": [
{
"counter": "copy_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} copy_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.
Copy a file or folder to a new location. It is categorised as a Write tool in the Apple Shortcuts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for copy_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 Apple Shortcuts. Nothing to install.
copy_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 copy_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 copy_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.
copy_file is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.