Update an existing Freshdesk ticket. Can update status, priority, assignee, type, tags, custom fields. For replies use reply_to_freshdesk_ticket; for notes use add_freshdesk_note.
Part of the Freshdesk MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use update_freshdesk_ticket to create or modify resources in Freshdesk. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_freshdesk_ticket repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Freshdesk.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
update_freshdesk_ticket:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Freshdesk policy for all 11 tools.
Agents calling write-class tools like update_freshdesk_ticket have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Update an existing Freshdesk ticket. Can update status, priority, assignee, type, tags, custom fields. For replies use reply_to_freshdesk_ticket; for notes use add_freshdesk_note.. 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.
Add a rule in your Intercept YAML policy under the tools section for update_freshdesk_ticket. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Freshdesk MCP server.
update_freshdesk_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_freshdesk_ticket rule in your Intercept 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 Intercept policy for update_freshdesk_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_freshdesk_ticket is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.