claim_forge
[Advanced] Build calldata to claim weekly $FORGE rewards. Proof is fetched from forgetreasury.com/rewards when omitted.
This record as markdown: /tools/com-forgetreasury-treasury/claim-forge.md
What claim_forge does on Forge Treasury
AI agents use claim_forge to commit financial operations through Forge Treasury, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
epoch | string | Yes | Reward epoch number |
proof | array | — | Merkle proof array (bytes32 hex strings). Optional — auto-fetched from manifest. |
amount | string | — | FORGE amount to claim (raw wei string). Optional if manifest has allocation. |
agentAddress | string | Yes | Agent wallet address |
Parameters from the server's own tool schema.
Why claim_forge is rated Critical
This tool builds and potentially submits calldata to claim $FORGE token rewards on Base mainnet. Claiming rewards constitutes a financial action as it moves tokens to the caller's wallet. Misuse could result in unauthorized reward claims or drain reward entitlements.
From the tool's definition 'claim weekly $FORGE rewards' and 'Build calldata to claim... rewards' — triggers on-chain financial transaction to claim token rewards
Attacks that exploit this kind of access
The rule that runs claim_forge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forge Treasury, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claim_forge, this is the rule to start with:
Any call to claim_forge is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Forge Treasury, apply this rule, and every claim_forge call is checked against it from then on.
Questions about claim_forge
[Advanced] Build calldata to claim weekly $FORGE rewards. Proof is fetched from forgetreasury.com/rewards when omitted. It is categorised as a Financial tool in the Forge Treasury MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
claim_forge accepts 4 parameters: epoch, proof, amount, agentAddress. Required: epoch, agentAddress. The full parameter table on this page comes from the server's own tool schema.
Register the Forge Treasury MCP server in PolicyLayer and add a rule for claim_forge: 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 Forge Treasury. Nothing to install.
claim_forge 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_forge 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_forge. 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_forge is provided by the Forge Treasury MCP server (https://mcp.forgetreasury.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Forge Treasury, and thousands of servers like it.
Across the catalogue