run_shortcut

Run a Siri Shortcut by name. Optionally provide text input. Returns the shortcut

SERVERIconnect SOURCEiconnect-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/run-shortcut.md

What run_shortcut does on Iconnect

AI agents invoke run_shortcut to trigger actions in Iconnect. 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 execution of user-defined automation workflows on macOS. An AI agent calling run_shortcut with an attacker-controlled shortcut name could invoke any installed shortcut, leading to uncontrolled side effects: data exfiltration, file deletion, credential theft, or malware propagation. The severity is critical because Shortcuts have deep system access and no sandboxing constraints.

From the tool's definition Tool description states 'Run a Siri Shortcut by name' — this executes code/automation workflows whose effects depend entirely on which shortcut is invoked and what it contains.

Questions about run_shortcut

What does the run_shortcut tool do? +

Run a Siri Shortcut by name. Optionally provide text input. Returns the shortcut. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_shortcut? +

Register the Iconnect 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 Iconnect. Nothing to install.

What risk level is run_shortcut? +

run_shortcut is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_shortcut? +

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.

How do I block run_shortcut completely? +

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.

What MCP server provides run_shortcut? +

run_shortcut is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Iconnect, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.