get_delivery_timeline
Read a delivery group planned/actual timeline and optional frozen-baseline variance, plus explanatory dependency risks. Unknown dates/history are not inferred. Bounded to 10,001 owned tickets (10,000 work tickets plus a root); pages of 1–500, default200. Critical path only for supported complete ...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-delivery-timeline.md
What get_delivery_timeline does on Meta Council
AI agents call get_delivery_timeline 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 |
|---|---|---|---|
limit | integer | — | |
root_id | string | Yes | |
baseline_id | string | — | |
after_ticket_id | string | — |
Parameters from the server's own tool schema.
Why get_delivery_timeline is rated Low
Even though get_delivery_timeline 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.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_delivery_timeline 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_delivery_timeline, this is the rule to start with:
get_delivery_timeline is read-only, so it stays allowed. 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 get_delivery_timeline call is checked against it from then on.
Questions about get_delivery_timeline
Read a delivery group planned/actual timeline and optional frozen-baseline variance, plus explanatory dependency risks. Unknown dates/history are not inferred. Bounded to 10,001 owned tickets (10,000 work tickets plus a root); pages of 1–500, default200. Critical path only for supported complete calendar/duration graphs; no dates move. Requires tickets:read. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_delivery_timeline accepts 4 parameters: limit, root_id, baseline_id, after_ticket_id. Required: root_id. 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 get_delivery_timeline: 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.
get_delivery_timeline is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_delivery_timeline 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 get_delivery_timeline. 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.
get_delivery_timeline 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