Creates a new sub-collection inside an existing eXist-db collection.
AI agents use existdb_create_collection to create or update resources in Existdb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Existdb environment.
Creating a collection is a write operation that modifies the database structure by adding new persistent data, but it is reversible—the collection can be deleted if needed. This distinguishes it from destructive operations. The blast radius is medium because malicious creation of collections could clutter the database or consume resources, but does not directly lose or corrupt existing data.
From the tool's definition The tool description states it 'Creates a new sub-collection inside an existing eXist-db collection.' The verb 'Creates' indicates data modification that is reversible (a collection can be deleted).
Documented attack patterns abuse exactly the kind of access existdb_create_collection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Existdb, and nothing reaches the server without passing your rules. This is the rule we recommend for existdb_create_collection:
{
"version": "1",
"default": "deny",
"tools": {
"existdb_create_collection": {
"limits": [
{
"counter": "existdb_create_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}existdb_create_collection 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.
Creates a new sub-collection inside an existing eXist-db collection. It is categorised as a Write tool in the Existdb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Existdb MCP server in PolicyLayer and add a rule for existdb_create_collection: 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 Existdb. Nothing to install.
existdb_create_collection 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 existdb_create_collection 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 existdb_create_collection. 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.
existdb_create_collection is provided by the Existdb MCP server (orazionelson/existdb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Existdb, 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.
12 Existdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.