grade_forum_user
Give a participant their whole-forum grade, as the forum's grader does: points ("7"), a scale item, or "none" to take it away; notify sends them Moodle's notification. Students may see it: confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/grade-forum-user.md
What grade_forum_user does on Moodle
AI agents invoke grade_forum_user to trigger actions in Moodle. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
user | string | — | The participant's alias, as the reading tools give it when the server pseudonymizes |
grade | string | Yes | |
notify | boolean | — | |
userId | integer | — | The participant's user id, when the server shows names |
forumId | integer | Yes | The forum's id (course module id) |
Parameters from the server's own tool schema.
Why grade_forum_user is rated High
grade_forum_user triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs grade_forum_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 grade_forum_user, this is the rule to start with:
grade_forum_user stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_forum_user call is checked against it from then on.
Questions about grade_forum_user
Give a participant their whole-forum grade, as the forum's grader does: points ("7"), a scale item, or "none" to take it away; notify sends them Moodle's notification. Students may see it: confirm with the person first. It is categorised as a Execute tool in the Moodle MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
grade_forum_user accepts 5 parameters: user, grade, notify, userId, forumId. Required: grade, forumId. 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_forum_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.
grade_forum_user is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the grade_forum_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 grade_forum_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.
grade_forum_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