win_loss_decoder
Analyse Win/Loss deals — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub — Win/Loss 32 deals Q1 2026 · Win rate 41% → 68% potentiel · Playbook 8 actions CRO. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/win-loss-decoder.md
What win_loss_decoder does on Gapup Mcp
AI agents use win_loss_decoder to commit financial operations through Gapup Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
deals | array | Yes | |
company | object | Yes | |
product | object | Yes | |
topCompetitors | array | — | |
primaryChallenge | string | — | |
salesCycleTargetDays | number | — |
Parameters from the server's own tool schema.
Why win_loss_decoder is rated Critical
The server is explicitly described as offering '271 agent-payable tools' with 'x402 per-call' billing, meaning each invocation commits a financial transaction. The tool itself is a win/loss analysis tool (Read/Execute in nature), but the payment-per-call model means every use incurs a financial obligation, making Financial the most severe applicable category.
From the tool's definition agent-payable, x402 per-call, C-suite expertise (CRO), Gapup Hub reference case
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
The rule that runs win_loss_decoder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For win_loss_decoder, this is the rule to start with:
Any call to win_loss_decoder is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every win_loss_decoder call is checked against it from then on.
Questions about win_loss_decoder
Analyse Win/Loss deals — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub — Win/Loss 32 deals Q1 2026 · Win rate 41% → 68% potentiel · Playbook 8 actions CRO. Inputs are validated server-side — send the documented case fields. It is categorised as a Financial tool in the Gapup Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
win_loss_decoder accepts 7 parameters: async, deals, company, product, topCompetitors, primaryChallenge, salesCycleTargetDays. Required: deals, company, product. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for win_loss_decoder: 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 Gapup Mcp. Nothing to install.
win_loss_decoder is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the win_loss_decoder 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 win_loss_decoder. 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.
win_loss_decoder is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
Across the catalogue