AI agents use triage_accept 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 |
|---|---|---|---|
project | string | Yes | Project slug |
ticket_ids | array | Yes | Array of ticket UUIDs to accept |
assignee_id | string | — | UUID of assignee |
target_status_id | string | Yes | UUID of target status to move tickets to |
Parameters from the server's own tool schema.
The tool updates ticket metadata (status field) but does not delete data or create irreversible changes. State transitions in project management systems are typically reversible—tickets can be re-triaged or moved to different statuses. The blast radius is medium because bulk acceptance of triaged tickets could misclassify work items and disrupt workflow, but changes can be undone.
From the tool's definition Tool description states 'move them to a target status', which modifies ticket state by transitioning from triage inbox to a different status. This is a reversible state change (tickets can be moved back or reassigned).
Attacks that exploit this kind of access
Accept tickets from triage inbox — move them to a target status. 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.
triage_accept accepts 4 parameters: project, ticket_ids, assignee_id, target_status_id. Required: project, ticket_ids, target_status_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 triage_accept: 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.
triage_accept 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 triage_accept 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 triage_accept. 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.
triage_accept 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 →