ticket_validation_finalize

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

Medium RISK CLASS

Category Write

Parameters 1110 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-validation-finalize.md

WHAT IT DOES

What ticket_validation_finalize does on Meta Council

AI agents use ticket_validation_finalize 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
`runner`	string	Yes
`summary`	string \| null	—
`verdict`	string	Yes
`evidence`	array	Yes
`ticket_id`	string	Yes
`environment`	string	Yes
`scenario_id`	string	Yes
`scenario_hash`	string	Yes
`idempotency_key`	string	Yes
`source_revision`	string	Yes
`scenario_version`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why ticket_validation_finalize is rated Medium

Creates a permanent, immutable validation record; irreversible but not destructive deletion.

From the tool's definition Finalize one immutable validation run... recorded but never opened

Risk signalsAccepts raw HTML/template content (evidence[].payload) · High parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_validation_finalize Rate-limited

ticket_validation_finalize 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_validation_finalize": {
      "limits": [
        {
          "counter": "ticket_validation_finalize_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_validation_finalize call is checked against it from then on.

FAQ

Questions about ticket_validation_finalize

What does the ticket_validation_finalize tool do? +

Finalize one immutable validation run for an exact owned ticket scenario revision. Requires the opt-in tickets:validate scope. The server derives owner and actor only from the authenticated API key. Evidence payloads are bounded opaque JSON objects; locator-looking strings are recorded but never opened, resolved, redirected, or fetched. Exact retries by the same credential actor return the original receipt; a changed actor or changed content under the same key conflicts. 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_validation_finalize accept? +

ticket_validation_finalize accepts 11 parameters: runner, summary, verdict, evidence, ticket_id, environment, scenario_id, scenario_hash, idempotency_key, source_revision, scenario_version. Required: runner, verdict, evidence, ticket_id, environment, scenario_id, scenario_hash, idempotency_key, source_revision, scenario_version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ticket_validation_finalize? +

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

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

Can I rate-limit ticket_validation_finalize? +

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

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

ticket_validation_finalize 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 →