assess_workshop_submission
Assess a workshop submission as the person, through the workshop's assessment form (its grading strategy's): a grade and comment per criterion in the form's order, overall feedback for the author (HTML), and any other field by name. A new assessment the first time, the same one changed after. Onl...
This record as markdown: /tools/falkenslab-moodle-mcp/assess-workshop-submission.md
What assess_workshop_submission does on Moodle
AI agents call assess_workshop_submission to retrieve information from Moodle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fields | object | — | Any other field of the form, by name |
criteria | array | — | In the form's order |
feedback | string | — | Overall feedback for the author (HTML); no aliases in it |
workshopId | integer | Yes | The workshop's id (course module id) |
submissionId | integer | Yes | As get_workshop gives it |
Parameters from the server's own tool schema.
Why assess_workshop_submission is rated Low
Even though assess_workshop_submission only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs assess_workshop_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 assess_workshop_submission, this is the rule to start with:
assess_workshop_submission is read-only, so it stays allowed. 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 assess_workshop_submission call is checked against it from then on.
Questions about assess_workshop_submission
Assess a workshop submission as the person, through the workshop's assessment form (its grading strategy's): a grade and comment per criterion in the form's order, overall feedback for the author (HTML), and any other field by name. A new assessment the first time, the same one changed after. Only in the assessment phase. Returns the grade it gives. The author reads it: confirm with the person first. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
assess_workshop_submission accepts 5 parameters: fields, criteria, feedback, workshopId, submissionId. Required: workshopId, submissionId. 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 assess_workshop_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.
assess_workshop_submission is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the assess_workshop_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 assess_workshop_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.
assess_workshop_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