funding_hunter
Chasseur de financements — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: PME deeptech cleantech FR €8M CA — top 30 dispositifs BPI+France2030+EU+VC. Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/funding-hunter.md
What funding_hunter does on Gapup Mcp
AI agents use funding_hunter 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 |
company | object | Yes | |
project | object | Yes | |
financials | object | Yes | |
preferences | object | Yes |
Parameters from the server's own tool schema.
Why funding_hunter is rated Critical
This tool identifies and structures funding opportunities (grants, VC, public programs) for enterprises. It is agent-payable per-call and involves committing to or surfacing financial instruments and funding pathways. The core function is financial advisory — identifying funding mechanisms that could result in financial obligations or commitments — placing it firmly in the Financial category.
From the tool's definition Chasseur de financements — CFO expertise, top 30 dispositifs BPI+France2030+EU+VC, agent-payable (x402 per-call)
Risk signalsHigh parameter count (26 properties)
Attacks that exploit this kind of access
The rule that runs funding_hunter 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 funding_hunter, this is the rule to start with:
Any call to funding_hunter 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 funding_hunter call is checked against it from then on.
Questions about funding_hunter
Chasseur de financements — Gapup agent-payable C-suite expertise (CFO). Returns a structured, audited deliverable. Reference case: PME deeptech cleantech FR €8M CA — top 30 dispositifs BPI+France2030+EU+VC. 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.
funding_hunter accepts 5 parameters: async, company, project, financials, preferences. Required: company, project, financials, preferences. 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 funding_hunter: 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.
funding_hunter 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 funding_hunter 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 funding_hunter. 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.
funding_hunter 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