Cancel an enrollment
AI agents call cancel_enrollment 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.
Cancelling an enrollment destroys or fundamentally alters the state of a critical educational record. This action cannot be reversed by the tool itself and would require manual intervention or a separate 're-enrollment' process to undo. The blast radius includes loss of course access, transcript records, and potential financial/administrative consequences.
From the tool's definition The tool is named 'cancel_enrollment' and described as 'Cancel an enrollment'. Cancellation of an enrollment is an irreversible operation that terminates a student's academic registration and cannot be undone without recreating the enrollment through separate…
Attacks that exploit this kind of access
Cancel an enrollment. 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 cancel_enrollment: 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.
cancel_enrollment 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 cancel_enrollment 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 cancel_enrollment. 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.
cancel_enrollment 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 →