deposit
Deposit USDC into a Forge Treasury vault on Base. Returns calldata for the agent wallet to sign. The agent must approve USDC to the vault contract first. Mints yield-bearing fUSDC shares. Conservative deposits Core only (single leg). Balanced returns two legs (50% Core / 50% Middle). Aggressive i...
This record as markdown: /tools/com-forgetreasury-treasury/deposit.md
What deposit does on Forge Treasury
AI agents use deposit 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 |
|---|---|---|---|
amount | string | Yes | USDC amount to deposit (human-readable, e.g. "1000" for 1000 USDC) |
profile | string | — | Strategy id (legacy "profile" name). conservative → Core vault. balanced → Core + Middle legs (50/50). aggressive → STRATEGY_NOT_LIVE. Defaults to "conservative |
agentAddress | string | Yes | Agent wallet address that will receive vault shares |
Parameters from the server's own tool schema.
Why deposit is rated Critical
This tool directly moves USDC (a stablecoin representing real financial value) from an agent's wallet into a yield vault on Base mainnet. This is a core Financial operation that commits monetary assets and creates yield-bearing positions. Even though it is non-custodial (user retains control), the tool enables irreversible capital deployment that obligates funds to a smart contract protocol.
From the tool's definition Tool description explicitly states 'Deposit USDC into a Forge Treasury vault' and 'The agent must approve USDC to the vault contract first'.
Attacks that exploit this kind of access
The rule that runs deposit 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 deposit, this is the rule to start with:
Any call to deposit 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 deposit call is checked against it from then on.
Questions about deposit
Deposit USDC into a Forge Treasury vault on Base. Returns calldata for the agent wallet to sign. The agent must approve USDC to the vault contract first. Mints yield-bearing fUSDC shares. Conservative deposits Core only (single leg). Balanced returns two legs (50% Core / 50% Middle). Aggressive is not live. Gas: Core 4M, Middle 6M+ on mainnet. 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.
deposit accepts 3 parameters: amount, profile, agentAddress. Required: amount, 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 deposit: 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.
deposit 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 deposit 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 deposit. 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.
deposit 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