Run a named Apple Shortcut, optionally with text input. Use this tool to execute any shortcut the user has in their Shortcuts library. Args: - name (string): The exact name or identifier of the shortcut to run. - input (string, optional): Text content to pass to the shortcut. Pass the literal tex...
AI agents invoke apple_shortcuts_run to trigger actions in Apple Shortcuts. 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.
This tool executes user-defined shortcuts on macOS, which are essentially automation sequences that can trigger any action available to the user's account. The effects are entirely dependent on what the shortcuts contain—they could modify files, trigger network operations, or invoke system commands.
From the tool's definition Tool description states it will "Run a named Apple Shortcut" and "execute any shortcut the user has in their Shortcuts library." Apple Shortcuts can perform arbitrary actions on the system including file operations, network requests, application automation,…
Documented attack patterns abuse exactly the kind of access apple_shortcuts_run 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 apple_shortcuts_run:
{
"version": "1",
"default": "deny",
"tools": {
"apple_shortcuts_run": {
"limits": [
{
"counter": "apple_shortcuts_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}apple_shortcuts_run 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.
Run a named Apple Shortcut, optionally with text input. Use this tool to execute any shortcut the user has in their Shortcuts library. Args: - name (string): The exact name or identifier of the shortcut to run. - input (string, optional): Text content to pass to the shortcut. Pass the literal text — the connector writes it to a private temporary file and hands that path to the macOS \. It is categorised as a Execute tool in the Apple Shortcuts MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for apple_shortcuts_run: 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.
apple_shortcuts_run 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 apple_shortcuts_run 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 apple_shortcuts_run. 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.
apple_shortcuts_run 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.