create_badge
Create a course badge, disabled and without criteria, through Moodle's new badge form: its name, description (plain text) and image (a local PNG, JPEG or GIF, at most 256 KB). Then set_badge_criteria gives it criteria and set_badge_enabled makes it available. Returns the badge. Changes the course...
This record as markdown: /tools/falkenslab-moodle-mcp/create-badge.md
What create_badge does on Moodle
AI agents use create_badge 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 |
|---|---|---|---|
name | string | Yes | |
image | string | Yes | An absolute local path to its image: PNG, JPEG or GIF, at most 256 KB |
courseId | integer | Yes | |
description | string | Yes | Plain text: Moodle strips tags |
imageCaption | string | — | The image's alternative text |
Parameters from the server's own tool schema.
Why create_badge is rated Medium
An AI agent can call create_badge 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.
Attacks that exploit this kind of access
The rule that runs create_badge 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 create_badge, this is the rule to start with:
create_badge 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 create_badge call is checked against it from then on.
Questions about create_badge
Create a course badge, disabled and without criteria, through Moodle's new badge form: its name, description (plain text) and image (a local PNG, JPEG or GIF, at most 256 KB). Then set_badge_criteria gives it criteria and set_badge_enabled makes it available. Returns the badge. 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.
create_badge accepts 5 parameters: name, image, courseId, description, imageCaption. Required: name, image, courseId, description. 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 create_badge: 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.
create_badge 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 create_badge 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 create_badge. 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.
create_badge 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