AI agents use create_ticket to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | |
scope | string | — | Scope tag, e.g. 'api', 'frontend' |
title | string | Yes | |
content | string | — | Markdown content (analysis, solution) |
project | string | Yes | Project slug, e.g. 'veliox' |
due_date | string | — | Due date in YYYY-MM-DD format |
priority | string | — | |
external_id | string | — | External identifier (e.g. JIRA-123, GH-456) |
affected_parts | array | — |
Parameters from the server's own tool schema.
This tool creates new project management entities (tickets) which are reversible—tickets can be deleted, modified, or archived. It has no permanent destructive effect, does not execute arbitrary code, involves no financial transactions, and is not a read-only query.
From the tool's definition Tool name 'create_ticket' and description 'Create a new ticket in a project' indicate data creation/modification in the project management system.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
Create a new ticket in a project. It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_ticket accepts 9 parameters: type, scope, title, content, project, due_date, priority, external_id, affected_parts. Required: type, title, project. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr 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 Tickr. 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 Tickr MCP server (@k-system/tickr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →