solve_ticket · Zendesk MCP: Risk & Policy

WHAT IT DOES

What solve_ticket does on Zendesk

AI agents use solve_ticket 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 solve_ticket needs a policy

Solving a ticket changes its status to 'solved', which is a state modification in Zendesk. This is a reversible write operation (tickets can be reopened), not a destructive action. Misuse could prematurely close legitimate support tickets, hence medium severity.

From the tool's definition Solve a single Zendesk ticket by ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

solve_ticket Rate-limited

solve_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": {
    "solve_ticket": {
      "limits": [
        {
          "counter": "solve_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 Zendesk, so you can run agents against it safely.

FAQ

Questions about solve_ticket

What does the solve_ticket tool do? +

Solve a single Zendesk ticket by ID. 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 solve_ticket? +

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

What risk level is solve_ticket? +

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

Can I rate-limit solve_ticket? +

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

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

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