Remove a contact
AI agents call remove_enrollment to permanently remove resources in Systemeio — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name suggests removing an enrollment (irreversible removal of course access), and the description 'Remove a contact' further implies deletion. In context of sibling tools like 'delete_contact' and 'enroll_contact_in_course', this likely removes a contact's course enrollment irreversibly.
From the tool's definition Tool name: 'remove_enrollment'; description: 'Remove a contact' — implies removing/deleting an enrollment or contact record, which is an irreversible deletion action.
Attacks that exploit this kind of access
Remove a contact. It is categorised as a Destructive tool in the Systemeio MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Systemeio MCP server in PolicyLayer and add a rule for remove_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 Systemeio. Nothing to install.
remove_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 remove_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 remove_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.
remove_enrollment is provided by the Systemeio MCP server (snzeeee/mcp-server-systemeio). 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 →