Submit a task ID and wait for it to complete. Polls automatically.
AI agents invoke wait_for_runway_task 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.
Although framed as a 'wait' operation, this tool executes an external workflow/task via the Runway platform. Since it triggers task completion and depends on arbitrary task IDs to determine effects, it falls under Execute rather than Read. The severity is medium because the blast radius depends on what the underlying Runway task does, but the tool itself initiates external operations.
From the tool's definition The tool 'wait_for_runway_task' accepts a task ID and 'waits for it to complete' with automatic polling. This triggers execution of an external operation (a Runway task) whose effects depend on the task ID argument provided.
Documented attack patterns abuse exactly the kind of access wait_for_runway_task 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 wait_for_runway_task:
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_runway_task": {
"limits": [
{
"counter": "wait_for_runway_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} wait_for_runway_task 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.
Submit a task ID and wait for it to complete. Polls automatically. 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 wait_for_runway_task: 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.
wait_for_runway_task 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 wait_for_runway_task 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 wait_for_runway_task. 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.
wait_for_runway_task 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.