Compute pipeline coverage from the user's own numbers and judge it against StackSwap's 2.5x-4x weighted band. Pass quota plus either openPipeline (a single total -> raw coverage only) or stages (an array of {amount, winRate} -> stage-WEIGHTED coverage, the number that actually matters). Returns r...
AI agents call compute_pipeline_coverage 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 |
|---|---|---|---|
quota | number | Yes | The quota / target to cover (same currency as pipeline). |
stages | array | — | Stage breakdown for weighted coverage. Each item: {amount, winRate (0-100, the historical win rate of that stage), label?}. |
openPipeline | number | — | Total open pipeline as a single number. Yields RAW coverage only. Prefer `stages` for the weighted number. |
Parameters from the server's own tool schema.
This tool retrieves and analyzes data provided by the user, performing mathematical computations and comparisons against benchmarks. It has no capability to modify, delete, or execute external operations. The explicit statement that it operates only on user-supplied figures and does not fetch CRM data confirms it is purely analytical (Read).
From the tool's definition Tool description explicitly states it 'Compute[s] pipeline coverage from the user's own numbers' and 'Operates only on figures the user supplies — it does not fetch any CRM data.' It performs calculations and analysis on provided data with no side effects.
Attacks that exploit this kind of access
Compute pipeline coverage from the user's own numbers and judge it against StackSwap's 2.5x-4x weighted band. Pass quota plus either openPipeline (a single total -> raw coverage only) or stages (an array of {amount, winRate} -> stage-WEIGHTED coverage, the number that actually matters). Returns raw + weighted coverage, a verdict (short / healthy / possibly-inflated), and the pipeline gap to a 3x cushion. Operates only on figures the user supplies — it does not fetch any CRM data. Use when the user asks 'is my pipeline coverage healthy', 'do I have enough pipeline to hit quota', or pastes pipeline + quota numbers. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
compute_pipeline_coverage accepts 3 parameters: quota, stages, openPipeline. Required: quota. 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 compute_pipeline_coverage: 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.
compute_pipeline_coverage 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 compute_pipeline_coverage 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 compute_pipeline_coverage. 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.
compute_pipeline_coverage 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →