This record as markdown: /tools/io-github-kivanccakmak-yaver/run-shortcut.md
What run_shortcut does on Yaver
AI agents invoke run_shortcut to trigger actions in Yaver. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Shortcut name |
input | string | — | Input text |
Parameters from the server's own tool schema.
Why run_shortcut is rated High
Running Apple Shortcuts falls under Execute category because it triggers external operations whose effects are determined by the shortcut's contents and arguments. While not destructive by default, shortcuts have broad capability to perform side effects on the system (file manipulation, app launching, network activity).
From the tool's definition Tool explicitly stated as 'Run an Apple Shortcut (macOS only)'. Apple Shortcuts can execute arbitrary automation tasks including file operations, system commands, network requests, and third-party app interactions.
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 Yaver, 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 Yaver, apply this rule, and every run_shortcut call is checked against it from then on.
Questions about run_shortcut
Run an Apple Shortcut (macOS only). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_shortcut accepts 2 parameters: name, input. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue