ticket_create

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

Medium RISK CLASS

Category Write

Parameters 121 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-create.md

WHAT IT DOES

What ticket_create does on Meta Council

AI agents use ticket_create 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
`title`	string	Yes
`effort`	string	—
`labels`	array	—
`status`	string	—	New epics cannot be created already done; task statuses use the lifecycle authority.
`assignee`	string	—
`priority`	string	—
`parent_id`	string	—	Parent ticket UUID.
`session_id`	string	—
`action_type`	string	—
`description`	string	—	Open with one plain sentence saying what needs to happen and why it matters, for someone picking this up cold; put specifics and jargon after it.
`order_index`	integer	—
`ticket_type`	string \| null	—	Immutable ticket kind; omit or use null to infer from effort.

Parameters from the server's own tool schema.

RISK

Why ticket_create is rated Medium

An AI agent can call ticket_create 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.

Risk signalsHigh parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_create Rate-limited

ticket_create 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_create": {
      "limits": [
        {
          "counter": "ticket_create_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_create call is checked against it from then on.

FAQ

Questions about ticket_create

What does the ticket_create tool do? +

Create a ticket on the caller's board — optionally as a subticket via parent_id. Recommend degree of difficulty with effort (trivial|small|medium|large|epic) and the kind of work with action_type (strategy|implementation|research|validation|testing|coordination). The authenticated API-key UUID is stamped by the server as creator provenance; callers cannot supply or spoof it. Session/workflow ids are opaque metadata links only. New epics cannot be created already 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.

What parameters does ticket_create accept? +

ticket_create accepts 12 parameters: title, effort, labels, status, assignee, priority, parent_id, session_id, action_type, description, order_index, ticket_type. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ticket_create? +

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

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

Can I rate-limit ticket_create? +

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

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

ticket_create 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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