Delete a user (simulation - does not persist)
AI agents call fakestore_delete_user to permanently remove resources in Fake Store API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the description notes '(simulation - does not persist)', the tool performs a destructive operation—deletion of user data. Even in a simulated/test environment, deletion is inherently irreversible and cannot be undone by the tool itself. This is the most severe applicable category under the classification hierarchy (Destructive > Execute > Write).
From the tool's definition Tool name includes 'delete' and description states 'Delete a user'. The action irreversibly removes a user record from the system.
Attacks that exploit this kind of access
Delete a user (simulation - does not persist). It is categorised as a Destructive tool in the Fake Store API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fake Store API MCP Server MCP server in PolicyLayer and add a rule for fakestore_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 Fake Store API MCP Server. Nothing to install.
fakestore_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 fakestore_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 fakestore_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.
fakestore_delete_user is provided by the Fake Store API MCP Server MCP server (op-enny/mcp-server-fakestore). 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 →