AI agents use create_implementation_item 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 |
|---|---|---|---|
area | string | Yes | Area: Database, API, Frontend, MCP, etc. |
note | string | — | Additional note |
number | string | Yes | Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed) |
fileOrDetail | string | Yes | Specific file path or description of the work |
Parameters from the server's own tool schema.
This tool creates new implementation items within tickets, which modifies project state but does not irreversibly delete data or execute arbitrary code. It is a standard Write operation. Severity is medium because misuse could clutter tickets with spurious implementation items, requiring manual cleanup, but the impact is localized to a single ticket's implementation tracking and easily reversible.
From the tool's definition Tool name 'create_implementation_item' and description 'Add a new implementation item to a ticket' indicate creation of a new data entity. The verb 'Add' and context of a project management system confirm this is a reversible creation operation.
Attacks that exploit this kind of access
Add a new implementation item to a ticket. 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_implementation_item accepts 4 parameters: area, note, number, fileOrDetail. Required: area, number, fileOrDetail. 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_implementation_item: 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_implementation_item 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_implementation_item 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_implementation_item. 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_implementation_item 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 →