market_sizing
Dimensionnement marché TAM/SAM/SOM — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Gapup Hub — TAM/SAM/SOM IA décisionnelle C-suite Europe · TAM €48Md · SOM €280M Year-3. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/market-sizing.md
What market_sizing does on Gapup Mcp
AI agents use market_sizing 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 |
target | object | Yes | |
horizon | string | — | |
product | object | Yes | |
approach | array | — | |
competitorComps | array | — |
Parameters from the server's own tool schema.
Why market_sizing is rated Critical
This tool is explicitly described as 'agent-payable' with 'x402 per-call' billing, meaning each invocation commits a financial transaction. While the analytical output is a market sizing report (a Read/Write operation in nature), the payment obligation triggered per call places it in the Financial category under the 'commits financial obligations' rule.
From the tool's definition agent-payable, x402 per-call, C-suite expertise (CMO), financial market sizing TAM/SAM/SOM with audited deliverable
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs market_sizing 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 market_sizing, this is the rule to start with:
Any call to market_sizing 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 market_sizing call is checked against it from then on.
Questions about market_sizing
Dimensionnement marché TAM/SAM/SOM — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Gapup Hub — TAM/SAM/SOM IA décisionnelle C-suite Europe · TAM €48Md · SOM €280M Year-3. 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.
market_sizing accepts 6 parameters: async, target, horizon, product, approach, competitorComps. Required: target, 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 market_sizing: 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.
market_sizing 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 market_sizing 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 market_sizing. 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.
market_sizing 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