run_shortcut
Run a Siri Shortcut by name. Optionally provide text input. Returns the shortcut
This record as markdown: /tools/heznpc-airmcp/run-shortcut.md
What run_shortcut does on AirMCP
AI agents invoke run_shortcut to trigger actions in AirMCP. 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.
Why run_shortcut is rated High
This tool triggers external operations (Siri Shortcuts) whose effects are entirely dependent on shortcut logic and arguments provided. Shortcuts can create, modify, delete data, make financial transactions, send messages, or execute system commands — making the blast radius critical if an AI agent calls this without strict guardrails.
From the tool's definition 'Run a Siri Shortcut by name' — executes user-defined automation workflows that can perform arbitrary actions across the Apple ecosystem (file operations, system commands, app launches, data modifications).
Attacks that exploit this kind of access
The rule that runs run_shortcut safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_shortcut, this is the rule to start with:
run_shortcut 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every run_shortcut call is checked against it from then on.
Questions about run_shortcut
Run a Siri Shortcut by name. Optionally provide text input. Returns the shortcut. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for run_shortcut: 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 AirMCP. Nothing to install.
run_shortcut 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 run_shortcut 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 run_shortcut. 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.
run_shortcut is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue