answer_lesson_page
Go on in a lesson as the person: press a content page's button (by its label, or by its position from 1), or answer a question page's fields by name (an option's value for choice and select, text for text). Returns Moodle's feedback, if any, and the next page; reaching the end ends the attempt. A...
This record as markdown: /tools/falkenslab-moodle-mcp/answer-lesson-page.md
What answer_lesson_page does on Moodle
AI agents call answer_lesson_page 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 |
|---|---|---|---|
button | string | — | A content page's button, by its label |
responses | object | — | A question page's answers: field name → value, as get_lesson_page gives the fields |
activityId | integer | Yes | The activity's id (course module id), as get_course_structure gives it |
buttonPosition | integer | — | Or by its position, from 1 |
Parameters from the server's own tool schema.
Why answer_lesson_page is rated Low
Even though answer_lesson_page 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 answer_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 answer_lesson_page, this is the rule to start with:
answer_lesson_page 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 answer_lesson_page call is checked against it from then on.
Questions about answer_lesson_page
Go on in a lesson as the person: press a content page's button (by its label, or by its position from 1), or answer a question page's fields by name (an option's value for choice and select, text for text). Returns Moodle's feedback, if any, and the next page; reaching the end ends the attempt. Answers count towards the lesson's grade and can't be taken back. With the realistic trail it pauses to read the page first. It is categorised as a Read tool in the Moodle MCP Server, which means it retrieves data without modifying state.
answer_lesson_page accepts 4 parameters: button, responses, activityId, buttonPosition. Required: activityId. 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 answer_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.
answer_lesson_page 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 answer_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 answer_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.
answer_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