set_badge_criteria
Set a badge's criteria: completing activities (with completion tracking; all of them or any one), completing the course (with a minimum course grade and a date), or awarded by hand by people with some roles (any one of them by default); all says whether every criterion must be met or any one. A c...
This record as markdown: /tools/falkenslab-moodle-mcp/set-badge-criteria.md
What set_badge_criteria does on Moodle
AI agents use set_badge_criteria 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 |
|---|---|---|---|
all | boolean | — | With more than one criterion: all must be met, or any one |
manual | object | — | |
remove | array | — | Criteria to take away |
badgeId | integer | Yes | The badge's id, as list_badges gives it |
activities | object | — | |
courseCompletion | object | — |
Parameters from the server's own tool schema.
Why set_badge_criteria is rated Medium
An AI agent can call set_badge_criteria 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 (12 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_badge_criteria 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 set_badge_criteria, this is the rule to start with:
set_badge_criteria 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 set_badge_criteria call is checked against it from then on.
Questions about set_badge_criteria
Set a badge's criteria: completing activities (with completion tracking; all of them or any one), completing the course (with a minimum course grade and a date), or awarded by hand by people with some roles (any one of them by default); all says whether every criterion must be met or any one. A criterion given replaces that kind's settings, one in remove goes, one not given stays. Moodle lets criteria change only while the badge is disabled and nobody has it. Returns the criteria. Changes the course: 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.
set_badge_criteria accepts 6 parameters: all, manual, remove, badgeId, activities, courseCompletion. Required: badgeId. 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 set_badge_criteria: 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.
set_badge_criteria 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 set_badge_criteria 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 set_badge_criteria. 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.
set_badge_criteria 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