zendesk_add_comment
Add a public or internal comment to a Zendesk ticket.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/zendesk-add-comment.md
What zendesk_add_comment does on UnClick
AI agents use zendesk_add_comment to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Comment text |
email | string | Yes | Agent email address |
public | boolean | — | Public reply (default true) or internal note (false) |
api_token | string | Yes | Zendesk API token |
subdomain | string | Yes | Zendesk subdomain |
ticket_id | string | Yes | Ticket id |
Parameters from the server's own tool schema.
Why zendesk_add_comment is rated Medium
Adding comments to tickets creates new data records within Zendesk and modifies the ticket state, making this a Write operation. Severity is medium because comments can affect ticket workflows, customer communication, and support records, but the action is reversible (comments can typically be edited or deleted). The tool does not move money, execute arbitrary code, or permanently destroy data.
From the tool's definition Tool description states 'Add a public or internal comment to a Zendesk ticket' — the verb 'add' and the action of inserting comment data into a ticket system indicates creation/modification of data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs zendesk_add_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zendesk_add_comment, this is the rule to start with:
zendesk_add_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every zendesk_add_comment call is checked against it from then on.
Questions about zendesk_add_comment
Add a public or internal comment to a Zendesk ticket. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
zendesk_add_comment accepts 6 parameters: body, email, public, api_token, subdomain, ticket_id. Required: body, email, api_token, subdomain, ticket_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for zendesk_add_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 UnClick. Nothing to install.
zendesk_add_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zendesk_add_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.
Set action: deny in the PolicyLayer policy for zendesk_add_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.
zendesk_add_comment is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue