ticket_plan

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

Medium RISK CLASS

Category Write

Parameters 103 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-plan.md

WHAT IT DOES

What ticket_plan does on Meta Council

AI agents use ticket_plan 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
`mode`	string	Yes
`plan`	object	—
`model`	string	—
`prompt`	string	Yes
`context`	string \| null	—
`session_id`	string \| null	—
`auto_assign`	boolean	—
`max_tickets`	integer	—
`preview_token`	string	—	Exact preview_token returned by preview mode.
`idempotency_key`	string	Yes	Caller-stable visible-ASCII key. Reuse only for the exact same operation and payload.

Parameters from the server's own tool schema.

RISK

Why ticket_plan is rated Medium

This tool creates or modifies data (ticket trees) in a reversible manner through its commit operation. While preview mode is read-only and non-mutating, the primary purpose includes committing changes to ticket systems, which is a write operation.

From the tool's definition Tool description states it can "idempotently commit an owner-private ticket tree" and "To commit, combine that commit_payload with mode=commit".

Risk signalsHigh parameter count (34 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_plan Rate-limited

ticket_plan 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_plan": {
      "limits": [
        {
          "counter": "ticket_plan_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_plan call is checked against it from then on.

FAQ

Questions about ticket_plan

What does the ticket_plan tool do? +

Preview or idempotently commit an owner-private ticket tree generated from a planning prompt or supplied structured plan. Requires tickets:write. A preview without a supplied plan invokes the planner model and additionally requires councils:run; supplied-plan preview and commit are provider-free and need only tickets:write. Preview is non-mutating and returns the normalized commit payload, an exact preview_token, and deterministic predicted ticket IDs as JSON. To commit, combine that commit_payload with mode=commit, the caller-held idempotency_key, and that exact preview_token; the response returns the same IDs plus replay status. A caller-stable visible-ASCII idempotency_key is always required. This creates only in-platform planning tickets; it never runs them, sends, publishes, deletes, or changes an external provider. 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_plan accept? +

ticket_plan accepts 10 parameters: mode, plan, model, prompt, context, session_id, auto_assign, max_tickets, preview_token, idempotency_key. Required: mode, prompt, idempotency_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ticket_plan? +

Register the Meta Council MCP server in PolicyLayer and add a rule for ticket_plan: 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_plan? +

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

Can I rate-limit ticket_plan? +

Yes. Add a rate_limit block to the ticket_plan 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_plan completely? +

Set action: deny in the PolicyLayer policy for ticket_plan. 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_plan? +

ticket_plan 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

poc_plan on 05 Mcp A2a Solution Studio →emit_variant_plan on 0sec → The MCP Attack Database →

Guides

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