run_shortcut · Yaver MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`name`	string	Yes	Shortcut name
`input`	string	—	Input text

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why run_shortcut needs a policy

run_shortcut triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_shortcut Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_shortcut": {
      "limits": [
        {
          "counter": "run_shortcut_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about run_shortcut

What does the run_shortcut tool do? +

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.

What parameters does run_shortcut accept? +

run_shortcut accepts 2 parameters: name, input. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_shortcut? +

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.

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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.