AI agents use wikijs_manage_collections to create or update resources in Wiki Js — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wiki Js environment.
The name suggests managing (creating, updating, or organizing) collections in Wiki.js. 'Manage' typically implies write-level operations. However, with no description, the exact behavior is unknown. Given sibling tools include destructive operations (delete, cleanup, purge), this could also be destructive, but 'manage' most commonly implies write/update. Confidence is low due to empty description.
From the tool's definition Tool name 'wikijs_manage_collections' on a Wiki.js MCP server; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access wikijs_manage_collections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wiki Js, and nothing reaches the server without passing your rules. This is the rule we recommend for wikijs_manage_collections:
{
"version": "1",
"default": "deny",
"tools": {
"wikijs_manage_collections": {
"limits": [
{
"counter": "wikijs_manage_collections_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wikijs_manage_collections 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.
wikijs_manage_collections. It is categorised as a Write tool in the Wiki Js MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wiki Js MCP server in PolicyLayer and add a rule for wikijs_manage_collections: 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 Wiki Js. Nothing to install.
wikijs_manage_collections 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 wikijs_manage_collections 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 wikijs_manage_collections. 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.
wikijs_manage_collections is provided by the Wiki Js MCP server (talosdeus/wiki-js-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Wiki Js tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Wiki Js tools catalogued and risk-classified — across an index of 42,500+ MCP servers.