Modify an existing calendar event. Does NOT notify attendees by default.
AI agents use calendar_update to create or update resources in Mariana Google MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mariana Google MCP environment.
This tool creates or modifies calendar data reversibly. It does not delete (which would be Destructive), does not execute arbitrary code (which would be Execute), and does not move money (which would be Financial). The reversible nature of calendar updates and the safety measure of not auto-notifying attendees keep this in Write category.
From the tool's definition Tool name is 'calendar_update' and description states 'Modify an existing calendar event', which is a reversible data modification operation.
Attacks that exploit this kind of access
Modify an existing calendar event. Does NOT notify attendees by default. It is categorised as a Write tool in the Mariana Google MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mariana Google MCP server in PolicyLayer and add a rule for calendar_update: 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 Mariana Google MCP. Nothing to install.
calendar_update 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 calendar_update 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 calendar_update. 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.
calendar_update is provided by the Mariana Google MCP server (marianasmall/mariana-google-mcp). 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 →