AI agents use create_ticket to create or update resources in Pearlog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pearlog environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | string | — | Comma-separated tags. |
type | string | — | Ticket type. Defaults to 'task'. |
status | number | — | Status ID. Defaults to 3 (open/backlog). Use get_status_labels to see available statuses. |
userId | number | — | ID of the user to assign the ticket to. Use list_users to find user IDs. |
headline | string | Yes | Ticket title (required). |
priority | number | — | Priority: 0=none, 1=low, 2=medium, 3=high. |
planHours | number | — | Estimated hours to complete the ticket. |
projectId | number | Yes | ID of the project to create the ticket in (required). Use list_projects to find the ID. |
description | string | — | Detailed description of the ticket. |
dateToFinish | string | — | Due date in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
The tool creates new tickets/tasks, which is a reversible write operation. It modifies project state by adding a new record but does not delete, execute code, move money, or irreversibly change data. Severity is medium because misuse could create many spurious tickets cluttering the project, but this is reversible via deletion (as evidenced by the sibling 'delete_ticket' tool).
From the tool's definition Tool name is 'create_ticket' and description states 'Create a new ticket (task/bug/feature/etc.) in a Pearlog project.' This creates new data in the project management system.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Create a new ticket (task/bug/feature/etc.) in a Pearlog project. It is categorised as a Write tool in the Pearlog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_ticket accepts 10 parameters: tags, type, status, userId, headline, priority, planHours, projectId, description, dateToFinish. Required: headline, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog 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 Pearlog. 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 Pearlog MCP server (mcp-server-pearlog). 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 →