ticket_claim
Claim a ticket to work on: sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged). Refuses if another agent already has it in progress unless force=true. Follow up with ticket_comment progress updates and finish via ticket_update status='done'.
This record as markdown: /tools/com-meta-council-decision-intelligence/ticket-claim.md
What ticket_claim does on Meta Council
AI agents use ticket_claim to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | Take over a ticket another agent holds. |
assignee | string | Yes | Your agent name, e.g. 'claude_code_local'. |
ticket_id | string | Yes |
Parameters from the server's own tool schema.
Why ticket_claim is rated Medium
This tool modifies ticket state (assignee field, status field) in a reversible manner. While it can override another agent's claim with force=true, this is not destructive or financial—the prior assignment state remains audit-logged and the ticket state can be reassigned. It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states it "sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged)." These are state modifications to a ticket object that are reversible (assignment and workflow state can be changed).
Attacks that exploit this kind of access
The rule that runs ticket_claim safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ticket_claim, this is the rule to start with:
ticket_claim stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every ticket_claim call is checked against it from then on.
Questions about ticket_claim
Claim a ticket to work on: sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged). Refuses if another agent already has it in progress unless force=true. Follow up with ticket_comment progress updates and finish via ticket_update status='done'. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
ticket_claim accepts 3 parameters: force, assignee, ticket_id. Required: assignee, ticket_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for ticket_claim: 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 Meta Council. Nothing to install.
ticket_claim 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 ticket_claim 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 ticket_claim. 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.
ticket_claim is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue