qbr_auto
QBR automatique CSM — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub × Alan — QBR Q1 2026 · Health score 82/100 · Upsell €18k détecté · Renewal low risk. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/qbr-auto.md
What qbr_auto does on Gapup Mcp
AI agents use qbr_auto 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 |
|---|---|---|---|
wins | array | Yes | |
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 |
period | object | Yes | |
company | object | Yes | |
metrics | object | Yes | |
customer | object | Yes | |
challenges | array | Yes | |
nextQuarterGoals | array | Yes |
Parameters from the server's own tool schema.
Why qbr_auto is rated Critical
This tool is part of a server explicitly described as '271 agent-payable tools' with 'x402 per-call' billing, meaning each invocation commits a financial transaction. Beyond the per-call cost, the tool's purpose is to produce QBR (Quarterly Business Review) deliverables that identify upsell opportunities (e.g., '€18k détecté') and renewal risk assessments, directly influencing financial commitments and revenue…
From the tool's definition Upsell €18k détecté · Renewal low risk · agent-payable · x402 per-call · C-suite expertise (CRO)
Risk signalsHigh parameter count (22 properties)
Attacks that exploit this kind of access
The rule that runs qbr_auto 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 qbr_auto, this is the rule to start with:
Any call to qbr_auto 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 qbr_auto call is checked against it from then on.
Questions about qbr_auto
QBR automatique CSM — Gapup agent-payable C-suite expertise (CRO). Returns a structured, audited deliverable. Reference case: Gapup Hub × Alan — QBR Q1 2026 · Health score 82/100 · Upsell €18k détecté · Renewal low risk. 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.
qbr_auto accepts 8 parameters: wins, async, period, company, metrics, customer, challenges, nextQuarterGoals. Required: wins, period, company, metrics, customer, challenges, nextQuarterGoals. 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 qbr_auto: 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.
qbr_auto 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 qbr_auto 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 qbr_auto. 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.
qbr_auto 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