bulk_solve_tickets_by_type · Zendesk MCP: Risk & Policy

WHAT IT DOES

What bulk_solve_tickets_by_type does on Zendesk

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

Solving tickets changes their status in bulk (up to 100 at a time), which is a significant write operation. While ticket solving can sometimes be reversed by reopening tickets, it is a mass state-change operation with high blast radius if misused.

From the tool's definition Bulk solve all open/pending tickets of a specific type (by tag) assigned to the authenticated user. Max 100 per operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_solve_tickets_by_type Rate-limited

bulk_solve_tickets_by_type 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": {
    "bulk_solve_tickets_by_type": {
      "limits": [
        {
          "counter": "bulk_solve_tickets_by_type_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 bulk_solve_tickets_by_type

What does the bulk_solve_tickets_by_type tool do? +

Bulk solve all open/pending tickets of a specific type (by tag) assigned to the authenticated user. Max 100 per operation. 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 bulk_solve_tickets_by_type? +

Register the Zendesk MCP server in PolicyLayer and add a rule for bulk_solve_tickets_by_type: 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 bulk_solve_tickets_by_type? +

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

Can I rate-limit bulk_solve_tickets_by_type? +

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

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

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