Build Calendar event parameters for a notification.
AI agents use prepare_notification to create or update resources in Claude Sync — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Sync environment.
The tool prepares/builds calendar event parameters, which implies constructing or creating data structures for a notification event. This is a Write operation as it creates new data. However, 'prepare' and 'build parameters' could also imply it's just formatting data without persisting it, which would lower severity.
From the tool's definition Build Calendar event parameters for a notification
Attacks that exploit this kind of access
Build Calendar event parameters for a notification. It is categorised as a Write tool in the Claude Sync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Sync MCP server in PolicyLayer and add a rule for prepare_notification: 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 Claude Sync. Nothing to install.
prepare_notification 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 prepare_notification 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 prepare_notification. 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.
prepare_notification is provided by the Claude Sync MCP server (the-firmament/claude-sync). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →