lead_magnets
Aimants à leads — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Spendesk — Guide trésorerie startup SaaS B2B FR/EU (2024). Inputs are validated server-side — send the documented case fields.
This record as markdown: /tools/io-github-getgapup-gapup-mcp/lead-magnets.md
What lead_magnets does on Gapup Mcp
AI agents use lead_magnets 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 |
|---|---|---|---|
icp | object | 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 |
brand | object | Yes | |
leadMagnet | object | Yes |
Parameters from the server's own tool schema.
Why lead_magnets is rated Critical
The server is explicitly described as '271 agent-payable tools' with 'x402 per-call' billing, meaning each invocation commits a financial transaction. The tool itself is tagged as 'agent-payable' and relates to CMO-level lead magnet generation. The Financial category applies because invoking this tool directly incurs a monetary charge per call, constituting a financial obligation.
From the tool's definition agent-payable, x402 per-call, C-suite expertise (CMO), structured deliverable with financial reference case (Spendesk — Guide trésorerie startup SaaS B2B)
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs lead_magnets 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 lead_magnets, this is the rule to start with:
Any call to lead_magnets 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 lead_magnets call is checked against it from then on.
Questions about lead_magnets
Aimants à leads — Gapup agent-payable C-suite expertise (CMO). Returns a structured, audited deliverable. Reference case: Spendesk — Guide trésorerie startup SaaS B2B FR/EU (2024). 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.
lead_magnets accepts 4 parameters: icp, async, brand, leadMagnet. Required: icp, brand, leadMagnet. 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 lead_magnets: 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.
lead_magnets 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 lead_magnets 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 lead_magnets. 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.
lead_magnets 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