ticket_label_list

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

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What ticket_label_list does on Meta Council

AI agents call ticket_label_list to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`include_archived`	boolean	—

Parameters from the server's own tool schema.

RISK

Why ticket_label_list is rated Low

Even though ticket_label_list only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_label_list Allowed

ticket_label_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ticket_label_list": {}
  }
}

ALLOW ONLY 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_label_list call is checked against it from then on.

FAQ

Questions about ticket_label_list

What does the ticket_label_list tool do? +

List the private owner label catalog with retained assignment counts and separate non-archived open counts. Labels are metadata, never approval, priority, severity, assignee, readiness or access authority. No provider label writes. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does ticket_label_list accept? +

ticket_label_list accepts 1 parameter: include_archived. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ticket_label_list? +

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

ticket_label_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ticket_label_list? +

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

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

ticket_label_list 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →