create_discussion
Start a discussion in a Moodle forum, with optional attachments and embedded images (local files); a teacher can post announcements this way in the announcements forum. Returns the new discussion's id, and whether it's pinned and the person subscribed, read back. Posts as the person, visibly: con...
This record as markdown: /tools/falkenslab-moodle-mcp/create-discussion.md
What create_discussion does on Moodle
AI agents use create_discussion 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 |
|---|---|---|---|
embed | array | — | Absolute local files (images…) to embed in the HTML, which names each by its file name: <img src="shot.png"> |
files | array | — | Absolute local paths to attach |
fields | object | — | Other post form fields by name, e.g. {"pinned": true} for a teacher |
forumId | integer | Yes | The forum's id (course module id), as get_course_structure gives it |
message | string | Yes | The message (HTML); no aliases in it, since people read it |
subject | string | Yes | |
subscribe | boolean | — | Subscribe to the discussion; Moodle's default when missing |
Parameters from the server's own tool schema.
Why create_discussion is rated Medium
An AI agent can call create_discussion 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_discussion 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_discussion, this is the rule to start with:
create_discussion 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_discussion call is checked against it from then on.
Questions about create_discussion
Start a discussion in a Moodle forum, with optional attachments and embedded images (local files); a teacher can post announcements this way in the announcements forum. Returns the new discussion's id, and whether it's pinned and the person subscribed, read back. Posts as the person, visibly: confirm the text 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_discussion accepts 7 parameters: embed, files, fields, forumId, message, subject, subscribe. Required: forumId, message, subject. 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_discussion: 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_discussion 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_discussion 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_discussion. 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_discussion 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