remove_ticket_tags · Zendesk MCP: Risk & Policy

WHAT IT DOES

What remove_ticket_tags does on Zendesk

AI agents use remove_ticket_tags to create or update resources in Zendesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zendesk environment.

WHY IT NEEDS A POLICY

Why remove_ticket_tags needs a policy

Removing tags from a ticket modifies the ticket's metadata but is reversible (tags can be re-added). This is a Write operation — it changes existing data without permanently destroying records. Severity is medium because tag manipulation can affect ticket routing, automation triggers, and SLA workflows.

From the tool's definition Remove specific tags from a ticket without affecting other tags

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_ticket_tags Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_ticket_tags": {
      "limits": [
        {
          "counter": "remove_ticket_tags_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 Zendesk, so you can run agents against it safely.

FAQ

Questions about remove_ticket_tags

What does the remove_ticket_tags tool do? +

Remove specific tags from a ticket without affecting other tags. It is categorised as a Write tool in the Zendesk 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_ticket_tags? +

Register the Zendesk MCP server in PolicyLayer and add a rule for remove_ticket_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 Zendesk. Nothing to install.

What risk level is remove_ticket_tags? +

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

Can I rate-limit remove_ticket_tags? +

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

How do I block remove_ticket_tags completely? +

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

What MCP server provides remove_ticket_tags? +

remove_ticket_tags is provided by the Zendesk MCP server (kalchevs/zendesk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.