Create, get details, update, or delete calendars
AI agents call manage_calendars to permanently remove resources in Google Calendar MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly includes 'delete calendars' as one of its operations. Deleting a calendar is irreversible and can permanently remove all events within it, making Destructive the appropriate category. Per the severity rules, the most severe applicable category wins over Write or Read operations also present in this tool.
From the tool's definition Create, get details, update, or delete calendars
Attacks that exploit this kind of access
Create, get details, update, or delete calendars. It is categorised as a Destructive tool in the Google Calendar MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for manage_calendars: 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 Google Calendar MCP Server. Nothing to install.
manage_calendars is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the manage_calendars 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 manage_calendars. 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.
manage_calendars is provided by the Google Calendar MCP Server MCP server (kashyab19/google-calendar-mcp-server). 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 →