Remove a user from the firm.
AI agents call remove_user to permanently remove resources in Smokeball — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a firm is a destructive action that cannot be easily undone and results in loss of access, permissions, and potentially associated data. This qualifies as Destructive rather than Write because user removal is typically irreversible and has significant organizational consequences. The high severity reflects the substantial impact on firm operations and user access management.
From the tool's definition Tool name 'remove_user' combined with description 'Remove a user from the firm' indicates irreversible deletion or deactivation of a user account from the organizational system.
Attacks that exploit this kind of access
Remove a user from the firm. It is categorised as a Destructive tool in the Smokeball MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Smokeball MCP server in PolicyLayer and add a rule for remove_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 Smokeball. Nothing to install.
remove_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 remove_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 remove_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.
remove_user is provided by the Smokeball MCP server (rosenadvertising/smokeball-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 →