Delete a user from /users/ and clean up legacy permission paths (/data/appAdmins, appUploaders, betaUsers). Does NOT delete Firebase Auth account.
AI agents call delete_user to permanently remove resources in Planning Game — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes user data and their permission assignments across multiple system paths (/users/, /data/appAdmins, appUploaders, betaUsers). While it does not delete the Firebase Auth account itself, the removal of user records and permissions cannot be undone, making this a Destructive action with high blast radius if an AI agent were to misuse it (e.g., deleting active users, removing administrative…
From the tool's definition Tool name is 'delete_user' and description states 'Delete a user from /users/ and clean up legacy permission paths'. The verb 'Delete' combined with 'clean up' indicates irreversible removal of user records and associated permission data.
Attacks that exploit this kind of access
Delete a user from /users/ and clean up legacy permission paths (/data/appAdmins, appUploaders, betaUsers). Does NOT delete Firebase Auth account. It is categorised as a Destructive tool in the Planning Game MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Planning Game 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 Planning Game. 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 Planning Game MCP server (planning-game-mcp). 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 →