Export all clips from a collection. Returns a
AI agents invoke opus_export_collection 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.
The tool exports all clips from a collection, which triggers an external operation (file export) via the macOS shortcuts CLI. This is an Execute-category action as it runs an external process. Severity is high due to potential bulk data export. Confidence is low because the description is truncated ('Returns a') leaving the full behavior unclear.
From the tool's definition 'Export all clips from a collection' - triggers an export operation (external action); runs via macOS shortcuts CLI
Documented attack patterns abuse exactly the kind of access opus_export_collection 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 opus_export_collection:
{
"version": "1",
"default": "deny",
"tools": {
"opus_export_collection": {
"limits": [
{
"counter": "opus_export_collection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} opus_export_collection 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.
Export all clips from a collection. Returns a. 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 opus_export_collection: 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.
opus_export_collection 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 opus_export_collection 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 opus_export_collection. 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.
opus_export_collection 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.