ticket_transition

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/ticket-transition.md

WHAT IT DOES

What ticket_transition does on Meta Council

AI agents use ticket_transition 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
`status`	string	Yes
`ticket_id`	string	Yes
`expected_completed_at`	string	—
`completion_idempotency_key`	string	—
`expected_completion_record_id`	string	—

Parameters from the server's own tool schema.

RISK

Why ticket_transition is rated Medium

An AI agent can call ticket_transition faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ticket_transition 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_transition, this is the rule to start with:

ticket_transition Rate-limited

ticket_transition 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ticket_transition": {
      "limits": [
        {
          "counter": "ticket_transition_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every ticket_transition call is checked against it from then on.

FAQ

Questions about ticket_transition

What does the ticket_transition tool do? +

Change an owned ticket's status through the existing lifecycle gate. For an epic completion, persist completion_idempotency_key before calling and retry the same request after an uncertain response. Reopening a terminal epic requires the exact expected_completed_at and, for an attested completion, expected_completion_record_id from ticket_authority. Stale coordinates and unready completions refuse without changing status. Reconcile uncertain reopen responses with ticket_authority. Returns committed transition and ticket JSON. Requires tickets:write. 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.

What parameters does ticket_transition accept? +

ticket_transition accepts 5 parameters: status, ticket_id, expected_completed_at, completion_idempotency_key, expected_completion_record_id. Required: status, ticket_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ticket_transition? +

Register the Meta Council MCP server in PolicyLayer and add a rule for ticket_transition: 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.

What risk level is ticket_transition? +

ticket_transition is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ticket_transition? +

Yes. Add a rate_limit block to the ticket_transition 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.

How do I block ticket_transition completely? +

Set action: deny in the PolicyLayer policy for ticket_transition. 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.

What MCP server provides ticket_transition? +

ticket_transition 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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →