Delete a firm user mapping by ID.
AI agents call delete_firm_user_mapping 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.
The tool permanently removes a firm user mapping record, which cannot be undone. This is a classic destructive operation that deletes data. While not financial or broadly system-critical like deleting all users would be, it still irreversibly modifies the firm's user configuration and warrants high severity due to the potential operational impact if user mappings are critical to firm operations or access control.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete a firm user mapping by ID' - this is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a firm user mapping by ID. 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 delete_firm_user_mapping: 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.
delete_firm_user_mapping 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_firm_user_mapping 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_firm_user_mapping. 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_firm_user_mapping 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 →