remove_contact_tag
Remove a tag from a specific contact
This record as markdown: /tools/instantkom-mcp-server/remove-contact-tag.md
What remove_contact_tag does on instantKOM MCP Server
AI agents use remove_contact_tag to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.
Why remove_contact_tag is rated Medium
Removing a tag modifies contact data but is generally reversible (the tag can be re-added), so this falls under Write rather than Destructive. Misuse could affect segmentation and targeting logic for a contact, giving it medium severity.
From the tool's definition 'Remove a tag from a specific contact' — removes an association between a tag and a contact
Attacks that exploit this kind of access
The rule that runs remove_contact_tag safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_contact_tag, this is the rule to start with:
remove_contact_tag stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every remove_contact_tag call is checked against it from then on.
Questions about remove_contact_tag
Remove a tag from a specific contact. It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for remove_contact_tag: 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 instantKOM MCP Server. Nothing to install.
remove_contact_tag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the remove_contact_tag 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_tag. 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_tag is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue