Remove a teacher from a meeting or planning event.
AI agents call delete_planning_attendee 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.
The tool performs an irreversible deletion operation on a planning/meeting record by removing a teacher attendee. While the blast radius is contained to attendance records rather than cascading deletions, the action cannot be undone and represents permanent data removal. This is categorized as Destructive rather than Write because deletion is inherently irreversible and destructive in nature.
From the tool's definition Tool name contains 'delete' and description states 'Remove a teacher from a meeting or planning event' — this irreversibly removes an entity (teacher attendance record) from a system record.
Attacks that exploit this kind of access
Remove a teacher from a meeting or 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_attendee: 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_attendee 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_attendee 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_attendee. 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_attendee 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 →