Delete a user from the project
AI agents call delete-user to permanently remove resources in Openfort MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a user is an irreversible operation that removes data and cannot be undone without restoration from backups. This fits the Destructive category definition. Severity is high because deleting users could disrupt project operations, authentication, and user access, affecting multiple dependent systems. The confidence is high due to the explicit use of 'delete' language.
From the tool's definition Tool name is 'delete-user' with description 'Delete a user from the project'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a user from the project. It is categorised as a Destructive tool in the Openfort MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openfort 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 Openfort 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 Openfort MCP Server MCP server (openfort-xyz/-deprecated-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 →