grade_submission
Grade a participant in an assignment, as Moodle's grader does: a grade (simple grading), a rubric's levels or a marking guide's scores per criterion (ids from get_rubric) with remarks, feedback comments (HTML, when the assignment has them on), whether to notify the student, and any other grading ...
This record as markdown: /tools/falkenslab-moodle-mcp/grade-submission.md
What grade_submission does on Moodle
AI agents use grade_submission to create or update resources in Moodle, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moodle environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | — | The participant's alias, as the reading tools give it when the server pseudonymizes |
grade | string | — | The grade as text: a number within the range ("7.5"), or a scale item |
guide | object | — | A marking guide's score per criterion: criterion id → score |
fields | object | — | Other grading form fields by name, e.g. a rubric's levels |
notify | boolean | — | Notify the student; Moodle's default when missing |
rubric | object | — | A rubric's level per criterion: criterion id → level id, as get_rubric gives them |
userId | integer | — | The participant's user id, when the server shows names |
remarks | object | — | Remarks per criterion of a rubric or guide: criterion id → text; no aliases |
feedback | string | — | Feedback comments (HTML); no aliases in it, since the student reads it |
applyToGroup | boolean | — | In a group assignment: give the same grade and feedback to the whole group |
assignmentId | integer | Yes | The assignment's id (course module id), as list_assignments gives it |
feedbackFiles | array | — | Absolute local paths of feedback files to return to the student |
Parameters from the server's own tool schema.
Why grade_submission is rated Medium
An AI agent can call grade_submission faster than any human can review: one bad instruction and it creates or modifies resources in Moodle by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs grade_submission 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 grade_submission, this is the rule to start with:
grade_submission stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every grade_submission call is checked against it from then on.
Questions about grade_submission
Grade a participant in an assignment, as Moodle's grader does: a grade (simple grading), a rubric's levels or a marking guide's scores per criterion (ids from get_rubric) with remarks, feedback comments (HTML, when the assignment has them on), whether to notify the student, and any other grading field by name in fields. Takes the participant as get_submissions gives them: user (an alias) when the server pseudonymizes, else userId. Works with or without a submission. Returns the grade saved. Changes grades students may see: confirm with the person first. It is categorised as a Write tool in the Moodle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
grade_submission accepts 12 parameters: user, grade, guide, fields, notify, rubric, userId, remarks, feedback, applyToGroup, assignmentId, feedbackFiles. Required: assignmentId. 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 grade_submission: 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.
grade_submission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the grade_submission 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 grade_submission. 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.
grade_submission 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.
This server
Across the catalogue