AI agents use bookstack_manage_content 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.
While the tool description is empty, the server explicitly advertises 'full CRUD operations' for content management. The tool name 'manage_content' paired with siblings like 'bookstack_content_crud' strongly suggests write operations (create, update, potentially delete). Without evidence of financial impact or irreversible destruction, this is classified as Write rather than Destructive.
From the tool's definition Tool name 'bookstack_manage_content' combined with server description stating 'full CRUD operations for books, chapters, and pages' indicates create/update/delete capabilities.
Documented attack patterns abuse exactly the kind of access bookstack_manage_content 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_manage_content:
{
"version": "1",
"default": "deny",
"tools": {
"bookstack_manage_content": {
"limits": [
{
"counter": "bookstack_manage_content_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bookstack_manage_content 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_manage_content. 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_manage_content: 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_manage_content 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_manage_content 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_manage_content. 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_manage_content 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.