edit_section
Change a section: rename it, describe it, show or hide it (with its activities), restrict access to it, or move it after another section. Only what is given changes. Returns the course structure. Changes the course: confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/edit-section.md
What edit_section does on Moodle
AI agents use edit_section 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 | — | |
embed | array | — | Absolute local files (images…) to embed in the HTML, which names each by its file name: <img src="shot.png"> |
summary | string | — | Its description (HTML) |
visible | boolean | — | |
courseId | integer | Yes | The course's id, as list_courses gives it |
sectionId | integer | Yes | A section's id (not its number), as get_course_structure gives it |
restrictions | object | — | When students can open it ({ conditions: [] } removes them) |
afterSectionId | integer | — | Move it after this section |
Parameters from the server's own tool schema.
Why edit_section is rated Medium
An AI agent can call edit_section 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 (20 properties)
Attacks that exploit this kind of access
The rule that runs edit_section 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 edit_section, this is the rule to start with:
edit_section 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 edit_section call is checked against it from then on.
Questions about edit_section
Change a section: rename it, describe it, show or hide it (with its activities), restrict access to it, or move it after another section. Only what is given changes. Returns the course structure. 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.
edit_section accepts 8 parameters: name, embed, summary, visible, courseId, sectionId, restrictions, afterSectionId. Required: courseId, sectionId. 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 edit_section: 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.
edit_section 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 edit_section 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 edit_section. 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.
edit_section 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