get_ticket_burndown
Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary. Optionally scope to one epic's current subtree via root_id. Backfill (legacy_snapshot) rows seed state but never count as ...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-ticket-burndown.md
What get_ticket_burndown does on Meta Council
AI agents call get_ticket_burndown 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 |
|---|---|---|---|
days | integer | — | |
root_id | string | — | |
baseline_id | string | — | |
target_date | string | — | Optional plan-line end date, YYYY-MM-DD. Must be strictly after the window start. Omitting it leaves the output exactly as it is without a plan line. |
Parameters from the server's own tool schema.
Why get_ticket_burndown is rated Low
Even though get_ticket_burndown 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
The rule that runs get_ticket_burndown 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_burndown, this is the rule to start with:
get_ticket_burndown 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_ticket_burndown call is checked against it from then on.
Questions about get_ticket_burndown
Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary. Optionally scope to one epic's current subtree via root_id. Backfill (legacy_snapshot) rows seed state but never count as additions. days clamps to 7-180 (default 30). Optionally pass target_date to overlay a straight-line plan: an ideal series descending from the window-start remaining to zero on that date, for reading actual against plan. Alternatively pass baseline_id for exact frozen-task planned/actual JSON with coverage; this uses the same cohort and excludes epic estimates and later additions. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_ticket_burndown accepts 4 parameters: days, root_id, baseline_id, target_date. 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_ticket_burndown: 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_ticket_burndown 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_ticket_burndown 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_ticket_burndown. 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_ticket_burndown 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