delete_book_chapter
Delete a chapter with its files; deleting a chapter (not a subchapter) deletes its subchapters too. Returns the chapters afterwards. Can't be undone: confirm with the person first.
This record as markdown: /tools/falkenslab-moodle-mcp/delete-book-chapter.md
What delete_book_chapter does on Moodle
AI agents call delete_book_chapter to permanently remove resources in Moodle, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
bookId | integer | Yes | The book's id (course module id), as get_course_structure gives it |
chapterId | integer | Yes | The chapter's id, as list_book_chapters gives it |
Parameters from the server's own tool schema.
Why delete_book_chapter is rated Critical
An AI agent that decides to call delete_book_chapter doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Moodle is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete_book_chapter 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 delete_book_chapter, this is the rule to start with:
delete_book_chapter is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Moodle, apply this rule, and every delete_book_chapter call is checked against it from then on.
Questions about delete_book_chapter
Delete a chapter with its files; deleting a chapter (not a subchapter) deletes its subchapters too. Returns the chapters afterwards. Can't be undone: confirm with the person first. It is categorised as a Destructive tool in the Moodle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_book_chapter accepts 2 parameters: bookId, chapterId. Required: bookId, 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 delete_book_chapter: 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.
delete_book_chapter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_book_chapter 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 delete_book_chapter. 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.
delete_book_chapter 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.
Across the catalogue