override_workshop_grade
Override a grade Moodle calculated in a workshop: a submission's grade, or an assessment's grade for assessing (give one of the two ids, from get_workshop), with feedback for the author or the reviewer; remove: true takes the override away, so the calculated grade counts again. Returns the submis...
This record as markdown: /tools/falkenslab-moodle-mcp/override-workshop-grade.md
What override_workshop_grade does on Moodle
AI agents call override_workshop_grade 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 |
|---|---|---|---|
grade | integer | — | A whole number up to the workshop's grade for submission (or for assessment) |
remove | boolean | — | Take the override away instead |
feedback | string | — | HTML; no aliases in it |
workshopId | integer | Yes | The workshop's id (course module id) |
assessmentId | integer | — | |
submissionId | integer | — |
Parameters from the server's own tool schema.
Why override_workshop_grade is rated Critical
An AI agent that decides to call override_workshop_grade 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 override_workshop_grade 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 override_workshop_grade, this is the rule to start with:
override_workshop_grade 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 override_workshop_grade call is checked against it from then on.
Questions about override_workshop_grade
Override a grade Moodle calculated in a workshop: a submission's grade, or an assessment's grade for assessing (give one of the two ids, from get_workshop), with feedback for the author or the reviewer; remove: true takes the override away, so the calculated grade counts again. Returns the submission or assessment afterwards. Students see it: 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.
override_workshop_grade accepts 6 parameters: grade, remove, feedback, workshopId, assessmentId, submissionId. 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 override_workshop_grade: 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.
override_workshop_grade 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 override_workshop_grade 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 override_workshop_grade. 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.
override_workshop_grade 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