unenrol_user
Unenrol someone from a course: removes every enrolment of theirs the person may remove, with their roles and group memberships in the course; removed and kept name the enrolment methods. Their work in the course stays in Moodle but they lose access. Confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/unenrol-user.md
What unenrol_user does on Moodle
AI agents call unenrol_user to permanently remove resources in Moodle, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | — | The participant's alias, as the reading tools give it when the server pseudonymizes |
userId | integer | — | The participant's user id, when the server shows names |
courseId | integer | Yes |
Parameters from the server's own tool schema.
Why unenrol_user is rated Critical
An AI agent that decides to call unenrol_user doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Moodle is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs unenrol_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Moodle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unenrol_user, this is the rule to start with:
unenrol_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every unenrol_user call is checked against it from then on.
Questions about unenrol_user
Unenrol someone from a course: removes every enrolment of theirs the person may remove, with their roles and group memberships in the course; removed and kept name the enrolment methods. Their work in the course stays in Moodle but they lose access. Confirm with the person first. It is categorised as a Destructive tool in the Moodle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
unenrol_user accepts 3 parameters: user, userId, courseId. Required: courseId. The full parameter table on this page comes from the server's own tool schema.
Register the Moodle MCP server in PolicyLayer and add a rule for unenrol_user: 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 Moodle. Nothing to install.
unenrol_user 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 unenrol_user 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 unenrol_user. 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.
unenrol_user is provided by the Moodle MCP server (@falkenslab/moodle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Moodle, and thousands of servers like it.
Across the catalogue