edit_lesson_page
Change a lesson's page through its form in the lesson editor: title, contents, buttons or answers (given, they replace them all), options and other fields; only what is given changes, and a page keeps its type. A jump to a page the lesson doesn't have is refused before anything is saved. Changes ...
This record as markdown: /tools/falkenslab-moodle-mcp/edit-lesson-page.md
What edit_lesson_page does on Moodle
AI agents use edit_lesson_page 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 to embed in the contents, answers or responses |
title | string | — | |
fields | object | — | Any other field of the page's form, by name (layout, display…) |
pageId | integer | Yes | The page's id, as get_lesson_pages gives it |
answers | array | — | A question page's answers, in order (given, they replace them all); an essay or structural page's single row |
buttons | array | — | A content page's buttons, in order; given, they replace them all |
contents | string | — | The page's contents (HTML); local files it names (<img src="shot.png">) go in embed |
lessonId | integer | Yes | The lesson's id (course module id), as get_course_structure gives it |
caseSensitive | boolean | — | Short answer: answers compared case-sensitively |
multipleAnswers | boolean | — | Multichoice: more than one answer can be right |
Parameters from the server's own tool schema.
Why edit_lesson_page is rated Medium
An AI agent can call edit_lesson_page 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 (17 properties)
Attacks that exploit this kind of access
The rule that runs edit_lesson_page 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_lesson_page, this is the rule to start with:
edit_lesson_page 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_lesson_page call is checked against it from then on.
Questions about edit_lesson_page
Change a lesson's page through its form in the lesson editor: title, contents, buttons or answers (given, they replace them all), options and other fields; only what is given changes, and a page keeps its type. A jump to a page the lesson doesn't have is refused before anything is saved. 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_lesson_page accepts 10 parameters: embed, title, fields, pageId, answers, buttons, contents, lessonId, caseSensitive, multipleAnswers. Required: pageId, lessonId. 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_lesson_page: 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_lesson_page 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_lesson_page 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_lesson_page. 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_lesson_page 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