edit_wiki_page
Change a wiki page's content, the whole page or one section (a heading, as get_wiki_page's sections lists them), as its editor does: a new version, by the person. Refused while someone else has the page open in its editor: try again later. Returns the page. Confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/edit-wiki-page.md
What edit_wiki_page does on Moodle
AI agents use edit_wiki_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 content (HTML pages), which names each by its file name: <img src="shot.png"> |
pageId | integer | Yes | The page's id, as list_wiki_pages gives it |
wikiId | integer | Yes | The wiki's id (course module id), as get_course_structure gives it |
content | string | Yes | Replaces the page's, or the section's; no aliases in it |
section | string | — |
Parameters from the server's own tool schema.
Why edit_wiki_page is rated Medium
An AI agent can call edit_wiki_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 signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs edit_wiki_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_wiki_page, this is the rule to start with:
edit_wiki_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_wiki_page call is checked against it from then on.
Questions about edit_wiki_page
Change a wiki page's content, the whole page or one section (a heading, as get_wiki_page's sections lists them), as its editor does: a new version, by the person. Refused while someone else has the page open in its editor: try again later. Returns the page. 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_wiki_page accepts 5 parameters: embed, pageId, wikiId, content, section. Required: pageId, wikiId, content. 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_wiki_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_wiki_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_wiki_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_wiki_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_wiki_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