AI agents use opus_schedule_post to create or update resources in Apple Shortcuts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Shortcuts environment.
Scheduling a post for future publishing creates or modifies data (the schedule record itself) in a reversible manner. While it involves content management, it is not executing code, not destructive (can be unscheduled), and not financial.
From the tool's definition The tool 'opus_schedule_post' is described as 'Schedule a clip for future publishing.' This is a write operation that creates or modifies scheduling data, preparing content for future publication without immediately executing it.
Documented attack patterns abuse exactly the kind of access opus_schedule_post 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_schedule_post:
{
"version": "1",
"default": "deny",
"tools": {
"opus_schedule_post": {
"limits": [
{
"counter": "opus_schedule_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}opus_schedule_post stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Schedule a clip for future publishing. It is categorised as a Write tool in the Apple Shortcuts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for opus_schedule_post: 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_schedule_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the opus_schedule_post 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_schedule_post. 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_schedule_post 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.