Build a weighted sales forecast from the user's OPEN DEALS, bucketed into Commit (>=80% win), Best case (50-79%), Pipeline (20-49%), and Longshot (<20%). Returns raw + weighted (amount x win%) totals per band, the overall weighted forecast, a vs-quota gap (if quota is passed), and slipping-deal f...
AI agents call build_forecast to retrieve information from StackSwap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
deals | array | Yes | Open deals as loose records. Recognized fields (with aliases): amount/value/acv, stage/dealstage, winProb/probability, closeDate/closeInDays, account/company. |
quota | number | — | Optional quota/target to measure the weighted forecast against. |
config | object | — | Optional tuning. |
Parameters from the server's own tool schema.
The tool ingests deal data provided by the user and performs calculations/analysis, returning a computed forecast. It does not modify, delete, or execute anything externally. The server is described as 'read-only tools' and this tool only processes input data to produce analytical output. Severity is low as misuse would at worst produce misleading forecasts but causes no system side effects.
From the tool's definition Build a weighted sales forecast from the user's OPEN DEALS... Returns raw + weighted totals per band, the overall weighted forecast, a vs-quota gap... and slipping-deal flags
Attacks that exploit this kind of access
Build a weighted sales forecast from the user's OPEN DEALS, bucketed into Commit (>=80% win), Best case (50-79%), Pipeline (20-49%), and Longshot (<20%). Returns raw + weighted (amount x win%) totals per band, the overall weighted forecast, a vs-quota gap (if quota is passed), and slipping-deal flags (past close date, or beyond config.periodDays). Win% is taken from each deal or inferred from the stage name; pass config.stageProbabilities to calibrate. Accepts loosely-typed deal records (amount, stage, winProb/probability, closeDate normalized). Generalizes compute_pipeline_coverage from a single total to a full deal set, forecast-framed. Operates only on supplied deals — no CRM fetch. Use when the user asks 'what's my forecast', 'what's my commit vs best case', or pastes a deal list. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
build_forecast accepts 3 parameters: deals, quota, config. Required: deals. The full parameter table on this page comes from the server's own tool schema.
Register the StackSwap MCP server in PolicyLayer and add a rule for build_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 StackSwap. Nothing to install.
build_forecast 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 build_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 build_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.
build_forecast is provided by the StackSwap MCP server (StonesofCreation/stackswap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
build_forecast is one line of StackSwap's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →