Delete a collection from PocketBase. Requires admin authentication. This will permanently remove the collection and all its records.
AI agents call delete_collection to permanently remove resources in Ssakone Pocketbase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes an entire collection and all associated records from the database. There is no undo mechanism mentioned. The blast radius is critical—an AI agent with admin authentication could destroy significant portions of application data. While it requires admin authentication, this is a control boundary, not a category reassessment.
From the tool's definition Tool description explicitly states: 'Delete a collection from PocketBase' and 'This will permanently remove the collection and all its records.' The use of 'permanently remove' and deletion of entire collections with all contained records confirms…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Delete a collection from PocketBase. Requires admin authentication. This will permanently remove the collection and all its records. It is categorised as a Destructive tool in the Ssakone Pocketbase MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ssakone Pocketbase MCP server in PolicyLayer and add a rule for delete_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 Ssakone Pocketbase. Nothing to install.
delete_collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_collection is provided by the Ssakone Pocketbase MCP server (@iflow-mcp/ssakone-pocketbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →