Deletes a user
AI agents call delete_user to permanently remove resources in FluentCommunity Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a user is a destructive action that irreversibly removes an account and its associated data from the system. This falls under the Destructive category (not merely Write, which is reversible). Given this is a community management plugin, accidental or malicious user deletion could impact site operations, user access, and data integrity, warranting critical severity.
From the tool's definition Tool name 'delete_user' combined with description 'Deletes a user' explicitly indicates irreversible deletion of user accounts. This operation cannot be undone and removes all associated user data.
Attacks that exploit this kind of access
Deletes a user. It is categorised as a Destructive tool in the FluentCommunity Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FluentCommunity Manager 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 FluentCommunity Manager. 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 FluentCommunity Manager MCP server (wplaunchify/fluent-community-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 →