Remove a tag from a contact. tag_id: the ID of the tag to remove.
AI agents call remove_contact_tags 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 tag from a contact is a destructive operation that deletes the tag association. While not catastrophic, it cannot be trivially undone (the tag relationship is lost), and misuse could affect contact categorization, filtering, and workflows across the law firm's practice management system. Severity is medium because it affects metadata/tagging rather than core matter or financial data.
From the tool's definition 'Remove a tag from a contact' - the word 'remove' indicates deletion of the tag association from the contact record
Attacks that exploit this kind of access
Remove a tag from a contact. tag_id: the ID of the tag to remove. 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_contact_tags: 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_contact_tags 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_contact_tags 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_contact_tags. 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_contact_tags 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 →