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...
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs save_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 save_ticket_delivery_plan, this is the rule to start with:
save_ticket_delivery_plan 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every save_ticket_delivery_plan call is checked against it from then on.
Questions about 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: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.
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.
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.
save_ticket_delivery_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
This server
Across the catalogue