Delete a user by ID
AI agents call delete_user to permanently remove resources in FastAPI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a user record by ID, which cannot be undone. Deletion is irreversible destruction of data, placing it in the Destructive category. The severity is high because unauthorized deletion of user accounts could cause significant operational and user impact, though the blast radius depends on the number of users that could be deleted in a single misuse incident.
From the tool's definition Tool name 'delete_user' and description 'Delete a user by ID' explicitly indicate irreversible deletion of user data.
Attacks that exploit this kind of access
Delete a user by ID. It is categorised as a Destructive tool in the FastAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FastAPI 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 FastAPI MCP Server. 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 FastAPI MCP Server MCP server (teeps-heisenberg/mcp-server-fast-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 →