update_shelf
Update an existing shelf in BookStack.
This record as markdown: /tools/derron-knox-bookstack-mcp-server/update-shelf.md
What update_shelf does on BookStack MCP Server
AI agents use update_shelf to create or update resources in BookStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BookStack MCP Server environment.
Why update_shelf is rated Medium
This tool creates or modifies data reversibly. Updating a shelf changes its metadata or structure but does not delete it (unlike delete_shelf) or retrieve/export data (unlike export_* tools). The impact is bounded to the shelf being updated, making it Write rather than Execute.
From the tool's definition Tool name 'update_shelf' and description 'Update an existing shelf in BookStack' indicate modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_shelf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BookStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_shelf, this is the rule to start with:
update_shelf 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 BookStack MCP Server, apply this rule, and every update_shelf call is checked against it from then on.
Questions about update_shelf
Update an existing shelf in BookStack. It is categorised as a Write tool in the BookStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BookStack MCP Server MCP server in PolicyLayer and add a rule for update_shelf: 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 BookStack MCP Server. Nothing to install.
update_shelf 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 update_shelf 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 update_shelf. 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.
update_shelf is provided by the BookStack MCP Server MCP server (derron-knox/bookstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on BookStack MCP Server, and thousands of servers like it.
This server
Across the catalogue