This record as markdown: /tools/io-github-portel-dev-ncp/create-ticket.md
What create_ticket does on Ncp
AI agents use create_ticket to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why create_ticket is rated Medium
This tool creates new records in Zendesk, which is a reversible write operation. It does not delete, modify existing data irreversibly, execute arbitrary code, or involve financial transactions. The severity is medium because creating tickets could be abused to generate spam, harassment, or overwhelm support systems, but the action itself is not destructive and can potentially be mitigated or undone by support staff.
From the tool's definition Tool name 'create_ticket' and description 'Create Zendesk support ticket' indicate a write operation that creates new data (a support ticket) in an external system.
Attacks that exploit this kind of access
The rule that runs create_ticket safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_ticket, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every create_ticket call is checked against it from then on.
Questions about create_ticket
Create Zendesk support ticket. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for 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 Ncp. Nothing to install.
create_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_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_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_ticket is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue