remove_workshop_reviewer
Remove a reviewer's allocation to a submission: Moodle deletes their assessment of it. An assessment already graded is only deleted with evenIfAssessed, and its grade is lost. Returns the submission's reviewers afterwards. Confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/remove-workshop-reviewer.md
What remove_workshop_reviewer does on Moodle
AI agents call remove_workshop_reviewer 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 |
|---|---|---|---|
author | string | — | The submission's author's alias, when the server pseudonymizes |
authorId | integer | — | The submission's author's user id, when the server shows names |
reviewer | string | — | The reviewer's alias, when the server pseudonymizes |
reviewerId | integer | — | The reviewer's user id, when the server shows names |
workshopId | integer | Yes | The workshop's id (course module id) |
submissionId | integer | — | The submission, as get_workshop_allocation gives it; or its author |
evenIfAssessed | boolean | — | Also when they already assessed it (the assessment and its grade are deleted) |
Parameters from the server's own tool schema.
Why remove_workshop_reviewer is rated Critical
An AI agent that decides to call remove_workshop_reviewer 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.
Attacks that exploit this kind of access
The rule that runs remove_workshop_reviewer 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 remove_workshop_reviewer, this is the rule to start with:
remove_workshop_reviewer 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 remove_workshop_reviewer call is checked against it from then on.
Questions about remove_workshop_reviewer
Remove a reviewer's allocation to a submission: Moodle deletes their assessment of it. An assessment already graded is only deleted with evenIfAssessed, and its grade is lost. Returns the submission's reviewers afterwards. 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.
remove_workshop_reviewer accepts 7 parameters: author, authorId, reviewer, reviewerId, workshopId, submissionId, evenIfAssessed. Required: workshopId. 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 remove_workshop_reviewer: 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.
remove_workshop_reviewer 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_workshop_reviewer 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_workshop_reviewer. 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_workshop_reviewer 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