zendesk_update_ticket · Integrations MCP: Risk & Policy

WHAT IT DOES

What zendesk_update_ticket does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why zendesk_update_ticket needs a policy

This tool modifies existing support tickets in Zendesk, which can change ticket status, assignments, comments, or other fields. While reversible (tickets can be modified again), the blast radius is high because an AI agent could incorrectly update customer-facing tickets, change ticket priorities, reassign critical issues, or modify customer communications without proper validation.

From the tool's definition Tool name is 'zendesk_update_ticket' which updates an existing ticket in Zendesk, a customer support platform. The verb 'update' indicates data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zendesk_update_ticket Rate-limited

zendesk_update_ticket 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": {
    "zendesk_update_ticket": {
      "limits": [
        {
          "counter": "zendesk_update_ticket_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about zendesk_update_ticket

What does the zendesk_update_ticket tool do? +

zendesk_update_ticket. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zendesk_update_ticket? +

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

What risk level is zendesk_update_ticket? +

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

Can I rate-limit zendesk_update_ticket? +

Yes. Add a rate_limit block to the zendesk_update_ticket 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 zendesk_update_ticket completely? +

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

zendesk_update_ticket is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.