zendesk_create_ticket · Integrations MCP: Risk & Policy

WHAT IT DOES

What zendesk_create_ticket does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why zendesk_create_ticket needs a policy

Creating a ticket in Zendesk is a reversible write operation—it adds data to the system but can be modified or deleted later. It has moderate blast radius: an AI agent could create numerous unwanted tickets, spam the support queue, or create tickets with misleading information that wastes support team time. However, it's not destructive (reversible) or financial (no money moves), and doesn't execute arbitrary code.

From the tool's definition Tool name 'zendesk_create_ticket' indicates creation of a support ticket in Zendesk. Description is empty, but the function name clearly denotes a write operation that creates new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zendesk_create_ticket Rate-limited

zendesk_create_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zendesk_create_ticket": {
      "limits": [
        {
          "counter": "zendesk_create_ticket_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about zendesk_create_ticket

What does the zendesk_create_ticket tool do? +

zendesk_create_ticket. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zendesk_create_ticket? +

Register the Integrations MCP server in PolicyLayer and add a rule for zendesk_create_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 Integrations MCP. Nothing to install.

What risk level is zendesk_create_ticket? +

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

Can I rate-limit zendesk_create_ticket? +

Yes. Add a rate_limit block to the zendesk_create_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.

How do I block zendesk_create_ticket completely? +

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

What MCP server provides zendesk_create_ticket? +

zendesk_create_ticket is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.