remove_tag_by_name · Ontraport MCP Server MCP: Risk & Policy

WHAT IT DOES

What remove_tag_by_name does on Ontraport MCP Server

AI agents use remove_tag_by_name 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.

WHY IT NEEDS A POLICY

Why remove_tag_by_name needs a policy

Removing tags from contacts modifies CRM data but is generally reversible (tags can be re-added), placing it in the Write category. The blast radius is medium as bulk tag removal across multiple contacts could affect segmentation, automations, and workflows triggered by tag presence.

From the tool's definition Remove one or more tags from one or more contacts by tag name

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_tag_by_name Rate-limited

remove_tag_by_name 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_tag_by_name": {
      "limits": [
        {
          "counter": "remove_tag_by_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ontraport MCP Server, so you can run agents against it safely.

FAQ

Questions about remove_tag_by_name

What does the remove_tag_by_name tool do? +

Remove one or more tags from one or more contacts by tag name. If the tag name doesn. 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.

How do I enforce a policy on remove_tag_by_name? +

Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for remove_tag_by_name: 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.

What risk level is remove_tag_by_name? +

remove_tag_by_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_tag_by_name? +

Yes. Add a rate_limit block to the remove_tag_by_name 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.

How do I block remove_tag_by_name completely? +

Set action: deny in the PolicyLayer policy for remove_tag_by_name. 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.

What MCP server provides remove_tag_by_name? +

remove_tag_by_name 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.