get_feature_delivery_summary
Read one owned feature epic's current task completion, estimates, weekly delivery flow, lead/cycle evidence, risks and throughput scenario. Includes a separate retained-history view of scope additions/removals, estimate changes and accumulated blocked task-hours, with explicit incomplete/ambiguou...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-feature-delivery-summary.md
What get_feature_delivery_summary does on Meta Council
AI agents call get_feature_delivery_summary 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 |
|---|---|---|---|
weeks | integer | — | |
root_id | string | Yes |
Parameters from the server's own tool schema.
Why get_feature_delivery_summary is rated Low
Even though get_feature_delivery_summary 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_feature_delivery_summary 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_feature_delivery_summary, this is the rule to start with:
get_feature_delivery_summary 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_feature_delivery_summary call is checked against it from then on.
Questions about get_feature_delivery_summary
Read one owned feature epic's current task completion, estimates, weekly delivery flow, lead/cycle evidence, risks and throughput scenario. Includes a separate retained-history view of scope additions/removals, estimate changes and accumulated blocked task-hours, with explicit incomplete/ambiguous coverage. Scope history follows the delivery-group hierarchy, not V3 project placement; it is not a planned timeline. 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_feature_delivery_summary accepts 2 parameters: weeks, root_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_feature_delivery_summary: 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_feature_delivery_summary 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_feature_delivery_summary 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_feature_delivery_summary. 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_feature_delivery_summary 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