ticket_update

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-update.md

WHAT IT DOES

What ticket_update does on Meta Council

AI agents use ticket_update 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	—
`effort`	string	—
`labels`	array	—
`status`	string	—	Task moves are audited. Epic done or terminal reopen requires an explicit lifecycle operation with retry/version evidence.
`assignee`	string	—
`priority`	string	—
`parent_id`	string	—
`ticket_id`	string	Yes
`labels_add`	array	—
`session_id`	string	—
`action_type`	string	—
`description`	string	—

Parameters from the server's own tool schema.

RISK

Why ticket_update is rated Medium

An AI agent can call ticket_update 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 (23 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_update Rate-limited

ticket_update 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_update": {
      "limits": [
        {
          "counter": "ticket_update_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_update call is checked against it from then on.

FAQ

Questions about ticket_update

What does the ticket_update tool do? +

Update fields on an owned ticket — status moves (each one is auto-logged to the ticket's audit trail), reassignment, priority/effort/action_type recommendations, title/description edits, safe reparenting, opaque session/workflow links, effort points, order, and user-owned external refs. Clear flags are explicit so stdio clients never lose JSON nulls. System-owned provider, Accounting, plan, and batch refs are preserved and cannot be spoofed. The authenticated API-key UUID is stamped on the audit trail. Epic completion and terminal reopen fail closed on this generic tool until an explicit lifecycle operation supplies retry/version evidence. 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_update accept? +

ticket_update accepts 12 parameters: title, effort, labels, status, assignee, priority, parent_id, ticket_id, labels_add, session_id, action_type, description. Required: 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_update? +

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

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

Can I rate-limit ticket_update? +

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

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

ticket_update 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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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