Deletes an event from Google Calendar.
AI agents call delete_calendar_event to permanently remove resources in Langfuse Observability — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes calendar event data without possibility of recovery through normal means. While the blast radius is somewhat constrained to calendar events (not critical infrastructure), unauthorized deletion of calendar events could disrupt scheduling, meetings, and coordinations. This is a destructive action that cannot be undone through the tool itself.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Deletes an event from Google Calendar' — this is an irreversible deletion operation on external calendar data.
Attacks that exploit this kind of access
Deletes an event from Google Calendar. It is categorised as a Destructive tool in the Langfuse Observability MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Langfuse Observability MCP server in PolicyLayer and add a rule for delete_calendar_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 Langfuse Observability. Nothing to install.
delete_calendar_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_calendar_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_calendar_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_calendar_event is provided by the Langfuse Observability MCP server (langfuse-observability-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 →