list_wiki_pages
List the pages of a wiki's subwiki by title: each one's id, the pages it links to (those not created yet without an id) and its latest version (number, date, author as an alias when the server pseudonymizes). The person's subwiki unless groupId or participant choose another. Empty while it has no...
This record as markdown: /tools/falkenslab-moodle-mcp/list-wiki-pages.md
What list_wiki_pages does on Moodle
AI agents call list_wiki_pages to retrieve information from Moodle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | How many pages (50 by default, up to 200) |
offset | integer | — | How many pages to skip first (0 by default) |
wikiId | integer | Yes | The wiki's id (course module id), as get_course_structure gives it |
groupId | integer | — | A group's subwiki, in a wiki with groups; the person's own when missing |
participant | string | — | A participant's subwiki in an individual wiki, by alias when the server pseudonymizes |
participantId | integer | — | Or by user id, when the server shows names |
Parameters from the server's own tool schema.
Why list_wiki_pages is rated Low
Even though list_wiki_pages only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_wiki_pages 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 list_wiki_pages, this is the rule to start with:
list_wiki_pages is read-only, so it stays allowed. 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 list_wiki_pages call is checked against it from then on.
Questions about list_wiki_pages
List the pages of a wiki's subwiki by title: each one's id, the pages it links to (those not created yet without an id) and its latest version (number, date, author as an alias when the server pseudonymizes). The person's subwiki unless groupId or participant choose another. Empty while it has no pages. A page at a time: limit pages (50 by default) after skipping offset; more says whether there are others. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
list_wiki_pages accepts 6 parameters: limit, offset, wikiId, groupId, participant, participantId. Required: wikiId. 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 list_wiki_pages: 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.
list_wiki_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_wiki_pages 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 list_wiki_pages. 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.
list_wiki_pages 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