Remove one or more tags from one or more contacts by tag ID.
AI agents use remove_tag_by_id to create or update resources in Ontraport MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ontraport MCP Server environment.
Removing tags from contacts modifies CRM data (contact attributes) but is generally reversible — tags can be re-added. This is a Write operation with medium severity since it can affect multiple contacts at once but does not permanently delete records or move money.
From the tool's definition Remove one or more tags from one or more contacts by tag ID
Attacks that exploit this kind of access
Remove one or more tags from one or more contacts by tag ID. It is categorised as a Write tool in the Ontraport MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for remove_tag_by_id: 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 Ontraport MCP Server. Nothing to install.
remove_tag_by_id 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_tag_by_id 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_tag_by_id. 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_tag_by_id is provided by the Ontraport MCP Server MCP server (landonray/mcp-server). 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 →