delete_user

THE RISK

Critical Risk

The tool irreversibly deletes user records from the database. This is a destructive operation that cannot be undone. While it targets user accounts rather than financial systems, the irreversible deletion of authentication records represents a high-severity destructive action that could impact system access, data integrity, and user management.

From the tool's definition Tool name is 'delete_user' and description explicitly states 'Delete a user from a PocketBase auth collection. This action is irreversible.'

Documented attack patterns abuse exactly the kind of access delete_user gives an agent:

HOW TO CONTROL DELETE_USER

PolicyLayer is an MCP gateway — it sits between your AI agents and PocketBase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_user:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_user"
  ]
}

delete_user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register PocketBase MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More PocketBase MCP Server tools

Destructive delete_collection Delete an existing collection from PocketBase. This action is irreversible and will perman Destructive delete_record Delete a record from a PocketBase collection. This action is irreversible. Write logout Logout from PocketBase and clear the authentication session. Write authenticate_user Authenticate as user with email and password. Stores the token for subsequent requests. Write create_collection Create a new collection in PocketBase. Requires admin authentication. Validates schema str Write create_record Create a new record in a PocketBase collection. Requires admin authentication. Write create_user Create a new user in a PocketBase auth collection. Requires admin authentication. Write update_collection Update an existing collection in PocketBase. Requires admin authentication. Only provided

All 19 PocketBase MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in PocketBase MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete_user tool do? +

Delete a user from a PocketBase auth collection. This action is irreversible. It is categorised as a Destructive tool in the PocketBase MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_user? +

Register the PocketBase MCP Server 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 PocketBase MCP Server. Nothing to install.

What risk level is delete_user? +

delete_user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_user? +

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.

How do I block delete_user completely? +

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.

What MCP server provides delete_user? +

delete_user is provided by the PocketBase MCP Server MCP server (ssakone/pb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PocketBase MCP Server tool call.

Deterministic rules across all 19 PocketBase MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN POCKETBASE →

Free to start. No card required.

19 PocketBase MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT DELETE_USER ON POCKETBASE MCP SERVER DOES

// THE RISK

// HOW TO CONTROL DELETE_USER

// EXPLORE