create_ticket_comment · Zendesk MCP Server MCP

WHAT IT DOES

What create_ticket_comment does on Zendesk MCP Server

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

WHY IT NEEDS A POLICY

Why create_ticket_comment needs a policy

This tool creates new data (comments) within an existing ticket, which is a reversible write operation. It does not execute code, delete data, or move money. The severity is medium because misuse could add misleading or harmful comments to customer-facing support tickets, affecting customer trust and creating potential business impact, but the action itself is reversible (comments can be deleted or edited).

From the tool's definition Tool description states 'Create a new comment on an existing Zendesk ticket' — the verb 'create' and the action of adding new content to a ticket indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ticket_comment Rate-limited

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

FAQ

Questions about create_ticket_comment

What does the create_ticket_comment tool do? +

Create a new comment on an existing Zendesk ticket. It is categorised as a Write tool in the Zendesk 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 create_ticket_comment? +

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

What risk level is create_ticket_comment? +

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

Can I rate-limit create_ticket_comment? +

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

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

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