AI agents use update_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 |
|---|---|---|---|
note | string | — | |
number | string | Yes | Ticket display number, e.g. 'TKR-42' (legacy) or 'TKR-BUG-0042' (typed) |
status | string | — | |
item_id | string | Yes | Implementation item GUID (from get_ticket output) |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly by updating an implementation item, which is a core Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The medium severity reflects that unauthorized updates to ticket implementation details could corrupt project tracking, but changes are reversible through subsequent updates.
From the tool's definition Tool name 'update_implementation_item' and description 'Update an implementation item on a ticket' indicate modification of existing data within the Tickr project management system.
Attacks that exploit this kind of access
Update an implementation item on 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.
update_implementation_item accepts 4 parameters: note, number, status, item_id. Required: number, item_id. 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 update_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.
update_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 update_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 update_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.
update_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 →