Delete a planning event.
AI agents call delete_planning_event to permanently remove resources in Eduframe — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on planning event data. Deletion cannot be undone without external intervention (e.g., database restore). While the blast radius may be limited to a single planning event rather than bulk data, the destructive nature and lack of recoverability place it in the Destructive category, which supersedes Write, Execute, and Read.
From the tool's definition Tool name is 'delete_planning_event' and description states 'Delete a planning event.' The verb 'Delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a planning event. It is categorised as a Destructive tool in the Eduframe MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Eduframe MCP server in PolicyLayer and add a rule for delete_planning_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 Eduframe. Nothing to install.
delete_planning_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_planning_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_planning_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_planning_event is provided by the Eduframe MCP server (martijnpieters/eduframe-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 →