set_book_chapter_visibility
Show a chapter to students or hide it from them, as the table of contents' eye does: a chapter's subchapters go with it, and a subchapter of a hidden chapter stays hidden. Returns the chapters afterwards. Changes what students see: confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/set-book-chapter-visibility.md
What set_book_chapter_visibility does on Moodle
AI agents use set_book_chapter_visibility 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 |
|---|---|---|---|
bookId | integer | Yes | The book's id (course module id), as get_course_structure gives it |
visible | boolean | Yes | |
chapterId | integer | Yes | The chapter's id, as list_book_chapters gives it |
Parameters from the server's own tool schema.
Why set_book_chapter_visibility is rated Medium
An AI agent can call set_book_chapter_visibility 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.
Attacks that exploit this kind of access
The rule that runs set_book_chapter_visibility 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 set_book_chapter_visibility, this is the rule to start with:
set_book_chapter_visibility 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 set_book_chapter_visibility call is checked against it from then on.
Questions about set_book_chapter_visibility
Show a chapter to students or hide it from them, as the table of contents' eye does: a chapter's subchapters go with it, and a subchapter of a hidden chapter stays hidden. Returns the chapters afterwards. Changes what students see: 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.
set_book_chapter_visibility accepts 3 parameters: bookId, visible, chapterId. Required: bookId, visible, chapterId. 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 set_book_chapter_visibility: 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.
set_book_chapter_visibility 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 set_book_chapter_visibility 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 set_book_chapter_visibility. 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.
set_book_chapter_visibility 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