Delete an event from the calendar
AI agents call yaag_delete_event to permanently remove resources in YearAtAGlance MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of calendar events cannot be undone and represents permanent loss of user data. While not as severe as financial or system-level destruction, deleting calendar events is a destructive operation with clear blast radius if invoked by an AI agent without proper authorization or intent verification.
From the tool's definition Tool name 'yaag_delete_event' and description 'Delete an event from the calendar' explicitly indicate irreversible deletion of calendar data.
Attacks that exploit this kind of access
Delete an event from the calendar. It is categorised as a Destructive tool in the YearAtAGlance MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the YearAtAGlance MCP Server MCP server in PolicyLayer and add a rule for yaag_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 YearAtAGlance MCP Server. Nothing to install.
yaag_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 yaag_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 yaag_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.
yaag_delete_event is provided by the YearAtAGlance MCP Server MCP server (mindfullabai/yearataglance-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 →