New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

save_ticket_delivery_plan

Explicitly replace or clear a ticket plan. Dates and working-day duration are separate from points. Pass current expected_version; reuse exact request_id on retries. Changed saves atomically record immutable revision and plan_changed history. No automatic scheduling/execution. Requires tickets:wr...

SERVERMeta Council SOURCEhttps://meta-council.com/mcp
Medium RISK CLASS
Category Write
Parameters 44 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/save-ticket-delivery-plan.md

What save_ticket_delivery_plan does on Meta Council

AI agents use save_ticket_delivery_plan 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.

ParameterTypeRequiredDescription
plan object | null Yes
ticket_id string Yes
request_id string Yes
expected_version integer Yes

Parameters from the server's own tool schema.

Why save_ticket_delivery_plan is rated Medium

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

Questions about save_ticket_delivery_plan

What does the save_ticket_delivery_plan tool do? +

Explicitly replace or clear a ticket plan. Dates and working-day duration are separate from points. Pass current expected_version; reuse exact request_id on retries. Changed saves atomically record immutable revision and plan_changed history. No automatic scheduling/execution. Requires tickets:write. 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 save_ticket_delivery_plan accept? +

save_ticket_delivery_plan accepts 4 parameters: plan, ticket_id, request_id, expected_version. Required: plan, ticket_id, request_id, expected_version. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on save_ticket_delivery_plan? +

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

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

Can I rate-limit save_ticket_delivery_plan? +

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

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

save_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.

More on Meta Council, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Council's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.