Accept, decline, or tentatively accept an event invitation.
AI agents use respond_to_event 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.
This tool modifies the state of a calendar event invitation (accepting, declining, or marking as tentative). This is a reversible write operation — the response can typically be changed later. It does not delete data, execute code, or involve financial transactions.
From the tool's definition Accept, decline, or tentatively accept an event invitation
Documented attack patterns abuse exactly the kind of access respond_to_event 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 respond_to_event:
{
"version": "1",
"default": "deny",
"tools": {
"respond_to_event": {
"limits": [
{
"counter": "respond_to_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}respond_to_event 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.
Accept, decline, or tentatively accept an event invitation. 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 respond_to_event: 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.
respond_to_event 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 respond_to_event 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 respond_to_event. 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.
respond_to_event 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.