This record as markdown: /tools/ghl/remove-contact-tags.md
What remove_contact_tags does on Ghl
AI agents use remove_contact_tags to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | Yes | Tags to remove |
contactId | string | Yes | Contact ID |
Parameters from the server's own tool schema.
Why remove_contact_tags is rated Medium
Removing tags alters contact metadata but does not delete the contact or irreversibly destroy data. Tags can be re-applied, making this a Write operation. Misuse could affect segmentation, automation triggers, or workflows tied to those tags, hence medium severity.
From the tool's definition 'Remove tags from a contact' — modifies contact data by removing tags, which is a reversible write operation (tags can be re-added)
Attacks that exploit this kind of access
The rule that runs remove_contact_tags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_contact_tags, this is the rule to start with:
remove_contact_tags 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 Ghl, apply this rule, and every remove_contact_tags call is checked against it from then on.
Questions about remove_contact_tags
Remove tags from a contact. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
remove_contact_tags accepts 2 parameters: tags, contactId. Required: tags, contactId. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl 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 Ghl. Nothing to install.
remove_contact_tags 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_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 Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
This server
Across the catalogue