AI agents use bookstack_content_crud 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.
The tool name explicitly references CRUD operations. Since CRUD encompasses both destructive (delete) and write (create/update) operations, the most severe applicable category is Destructive. However, the description is empty, reducing confidence.
From the tool's definition Tool name contains 'crud' (Create, Read, Update, Delete) and the server description mentions 'full CRUD operations for books, chapters, and pages'
Documented attack patterns abuse exactly the kind of access bookstack_content_crud gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BookStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bookstack_content_crud:
{
"version": "1",
"default": "deny",
"tools": {
"bookstack_content_crud": {
"limits": [
{
"counter": "bookstack_content_crud_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bookstack_content_crud 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.
Free to start. No card required.
bookstack_content_crud. 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 bookstack_content_crud: 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.
bookstack_content_crud 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 bookstack_content_crud 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 bookstack_content_crud. 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.
bookstack_content_crud is provided by the BookStack MCP Server MCP server (oculairmedia/bookstack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BookStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 BookStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.