create_zendesk_ticket
Create a new Zendesk ticket. Required: subject and either comment (for new ticket with initial message) or description. Optional: priority, type, tags, assignee_id, group_id, custom_fields. For custom_fields, use list_zendesk_ticket_fields to find field IDs first. For group_id, use list_zendesk_g...
This record as markdown: /tools/freshdesk/create-zendesk-ticket.md
What create_zendesk_ticket does on Freshdesk
AI agents use create_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 create_zendesk_ticket is rated Medium
Creating a ticket is a reversible write operation that adds new data to the system. It does not execute arbitrary code, delete data, or move money. The impact is medium severity because ticket creation could spam support systems or create false tickets if misused by an AI agent, but the operation itself is non-destructive and can be undone.
From the tool's definition Tool description states 'Create a new Zendesk ticket' with required parameters like subject and comment/description, plus optional parameters for priority, assignee, groups, and custom fields. This is explicitly a creation operation that modifies data.
Attacks that exploit this kind of access
The rule that runs create_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 create_zendesk_ticket, this is the rule to start with:
create_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 create_zendesk_ticket call is checked against it from then on.
Questions about create_zendesk_ticket
Create a new Zendesk ticket. Required: subject and either comment (for new ticket with initial message) or description. Optional: priority, type, tags, assignee_id, group_id, custom_fields. For custom_fields, use list_zendesk_ticket_fields to find field IDs first. For group_id, use list_zendesk_groups to find available groups. Example: {. 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 create_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.
create_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 create_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 create_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.
create_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