Delete a teacher role.
AI agents call delete_teacher_role 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.
Deleting a teacher role is an irreversible operation that permanently removes an entity from the system. This cannot be undone without manual restoration and represents a destructive action on institutional data. The high severity reflects the potential impact on educational operations if a teacher role is mistakenly deleted—courses, assignments, or other role-linked data could be affected.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a teacher role.' The verb 'delete' combined with the irreversible nature of removing a teacher role from the system indicates destructive action.
Attacks that exploit this kind of access
Delete a teacher role. 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_teacher_role: 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_teacher_role 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_teacher_role 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_teacher_role. 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_teacher_role 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 →