AI agents call delete_event to permanently remove resources in Google Toolbox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes calendar events, which cannot be undone through the tool itself. While not as severe as full account compromise, accidental deletion of important events could disrupt scheduling, meetings, or organizational activities. The impact is high enough to warrant 'high' severity, as deletion is permanent and affects user data integrity.
From the tool's definition delete_event with description "Delete a calendar event" — the verb "Delete" combined with action on calendar data indicates irreversible removal of an event record.
Documented attack patterns abuse exactly the kind of access delete_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Toolbox, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_event:
{
"version": "1",
"default": "deny",
"hide": [
"delete_event"
]
}delete_event disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a calendar event. It is categorised as a Destructive tool in the Google Toolbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Toolbox MCP server in PolicyLayer and add a rule for delete_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 Google Toolbox. Nothing to install.
delete_event 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 delete_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 delete_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.
delete_event is provided by the Google Toolbox MCP server (jikime/py-mcp-google-toolbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Toolbox, 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.
11 Google Toolbox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.