update_zendesk_ticket
Update an existing Zendesk ticket. Can update status, priority, assignee, tags, custom fields, and add comments. Use add_comment to add a reply (public or internal note). Example - resolve with comment: {
This record as markdown: /tools/freshdesk/update-zendesk-ticket.md
What update_zendesk_ticket does on Freshdesk
AI agents use update_zendesk_ticket to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why update_zendesk_ticket is rated Medium
This tool modifies ticket metadata (status, priority, assignee, tags, custom fields) and adds comments to existing tickets. These are reversible changes typical of Write operations—data is created or modified but not destroyed. The severity is medium because unintended modifications could disrupt support workflows, ticket routing, or customer communication, though changes can be undone by subsequent updates.
From the tool's definition Update an existing Zendesk ticket. Can update status, priority, assignee, tags, custom fields, and add comments.
Attacks that exploit this kind of access
The rule that runs update_zendesk_ticket safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_zendesk_ticket, this is the rule to start with:
update_zendesk_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every update_zendesk_ticket call is checked against it from then on.
Questions about update_zendesk_ticket
Update an existing Zendesk ticket. Can update status, priority, assignee, tags, custom fields, and add comments. Use add_comment to add a reply (public or internal note). Example - resolve with comment: {. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for update_zendesk_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 Freshdesk. Nothing to install.
update_zendesk_ticket 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 update_zendesk_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.
Set action: deny in the PolicyLayer policy for update_zendesk_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.
update_zendesk_ticket is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue