Delete a user from a PocketBase auth collection. This permanently removes the user account.
AI agents call delete_user 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 irreversibly deletes user accounts. The operation cannot be undone without external backups or recovery procedures. While not financial in itself, deleting user accounts has a high blast radius as it affects authentication, access control, and can lock users out of systems. This is clearly Destructive rather than Write (which is reversible) or Execute (which has variable outcomes).
From the tool's definition Tool description explicitly states: 'Delete a user from a PocketBase auth collection. This permanently removes the user account.' The verb 'Delete' combined with 'permanently removes' indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a user from a PocketBase auth collection. This permanently removes the user account. 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_user: 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_user 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_user 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_user. 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_user 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 →