capture_feature_forecast
Explicitly save an immutable owner-private delivery scenario and minimal replay inputs for one epic's current descendants, including archives. Default window is eight UTC weeks. Reuse the same owner-wide request_id and exact arguments after an uncertain response; retries return the original captu...
This record as markdown: /tools/com-meta-council-decision-intelligence/capture-feature-forecast.md
What capture_feature_forecast does on Meta Council
AI agents use capture_feature_forecast 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 |
|---|---|---|---|
weeks | integer | — | |
root_id | string | Yes | |
request_id | string | Yes |
Parameters from the server's own tool schema.
Why capture_feature_forecast is rated Medium
An AI agent can call capture_feature_forecast 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 capture_feature_forecast 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 capture_feature_forecast, this is the rule to start with:
capture_feature_forecast 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 capture_feature_forecast call is checked against it from then on.
Questions about capture_feature_forecast
Explicitly save an immutable owner-private delivery scenario and minimal replay inputs for one epic's current descendants, including archives. Default window is eight UTC weeks. Reuse the same owner-wide request_id and exact arguments after an uncertain response; retries return the original capture even after source deletion. Missing history remains unavailable. No schedules, notifications or provider work. 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.
capture_feature_forecast accepts 3 parameters: weeks, root_id, request_id. Required: root_id, request_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 capture_feature_forecast: 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.
capture_feature_forecast 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 capture_feature_forecast 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 capture_feature_forecast. 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.
capture_feature_forecast 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