get_ticket_delivery_plan

Read the explicit dated plan of an owned ticket, including archived or retained deleted-ticket plans. Absent plans remain unknown. Requires tickets:read.

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

Low RISK CLASS

Category Read

Parameters 11 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/get-ticket-delivery-plan.md

WHAT IT DOES

What get_ticket_delivery_plan does on Meta Council

AI agents call get_ticket_delivery_plan 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
`ticket_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_ticket_delivery_plan is rated Low

Even though get_ticket_delivery_plan 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 get_ticket_delivery_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 get_ticket_delivery_plan, this is the rule to start with:

get_ticket_delivery_plan Allowed

get_ticket_delivery_plan 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": {
    "get_ticket_delivery_plan": {}
  }
}

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

FAQ

Questions about get_ticket_delivery_plan

What does the get_ticket_delivery_plan tool do? +

Read the explicit dated plan of an owned ticket, including archived or retained deleted-ticket plans. Absent plans remain unknown. Requires tickets:read. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does get_ticket_delivery_plan accept? +

get_ticket_delivery_plan accepts 1 parameter: ticket_id. 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 get_ticket_delivery_plan? +

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

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

Can I rate-limit get_ticket_delivery_plan? +

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

Set action: deny in the PolicyLayer policy for get_ticket_delivery_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 get_ticket_delivery_plan? +

get_ticket_delivery_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

aiva_get_delivery_schedule on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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