claim_donation
Bind an on-chain donation (Base ETH or USDC sent to the wallet) to your handle and collect the founder's-discount reward: ~5x its USD value in ▲ credits (first patrons) + the Founding Patron badge. Idempotent on the tx hash — claiming twice is a no-op. Requires your handle + secret so the reward ...
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/claim-donation.md
What claim_donation does on Gateway
AI agents use claim_donation to commit financial operations through Gateway, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | your registered handle |
secret | string | — | your agent secret (or send as Bearer) |
tx_hash | string | Yes | the 0x… hash of your donation tx on Base |
Parameters from the server's own tool schema.
Why claim_donation is rated Critical
This tool processes on-chain cryptocurrency transactions (Base ETH or USDC), binds financial transfers to user accounts, and distributes credits/rewards. It directly involves financial obligations and on-chain asset movements, placing it firmly in the Financial category. Misuse could lead to fraudulent reward claims or credential exposure via the required secret.
From the tool's definition Bind an on-chain donation (Base ETH or USDC sent to the wallet) ... collect the founder's-discount reward: ~5x its USD value in ▲ credits ... Requires your handle + secret so the reward can be credited to you.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs claim_donation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claim_donation, this is the rule to start with:
Any call to claim_donation is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every claim_donation call is checked against it from then on.
Questions about claim_donation
Bind an on-chain donation (Base ETH or USDC sent to the wallet) to your handle and collect the founder's-discount reward: ~5x its USD value in ▲ credits (first patrons) + the Founding Patron badge. Idempotent on the tx hash — claiming twice is a no-op. Requires your handle + secret so the reward can be credited to you. It is categorised as a Financial tool in the Gateway MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
claim_donation accepts 3 parameters: handle, secret, tx_hash. Required: handle, tx_hash. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for claim_donation: 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 Gateway. Nothing to install.
claim_donation 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 claim_donation 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 claim_donation. 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.
claim_donation is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue