canvas_delete_calendar_event
AI agents call canvas_delete_calendar_event to permanently remove resources in Canvas LMS 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 is irreversible; once removed, the event cannot be recovered without administrative intervention. An AI agent with access to this tool could maliciously or accidentally delete important academic deadlines, exam dates, or personal calendar entries from the user's Canvas account.
From the tool's definition Tool name 'canvas_delete_calendar_event' contains the verb 'delete', which performs irreversible removal of data. The server description confirms this is Canvas LMS functionality for a student account.
Attacks that exploit this kind of access
canvas_delete_calendar_event. It is categorised as a Destructive tool in the Canvas LMS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Canvas LMS MCP Server MCP server in PolicyLayer and add a rule for canvas_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 Canvas LMS MCP Server. Nothing to install.
canvas_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 canvas_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 canvas_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.
canvas_delete_calendar_event is provided by the Canvas LMS MCP Server MCP server (sweeden-ttu/canvas-lms-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 →