simulate_deposit
Project expected returns for a USDC deposit over 30, 90, and 365 days using the blended target APY. Use for agent reasoning before depositing. APY is a blended target across conservative allocation weights; not a guarantee. Sepolia uses MockYieldAdapter until mainnet adapters are live.
This record as markdown: /tools/com-forgetreasury-treasury/simulate-deposit.md
What simulate_deposit does on Forge Treasury
AI agents call simulate_deposit to retrieve information from Forge Treasury without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | string | Yes | USDC amount to simulate (e.g. "10000") |
profile | string | — | Risk profile to simulate. MVP: "conservative" only. Defaults to "conservative". balanced/aggressive return PROFILE_NOT_LIVE. |
Parameters from the server's own tool schema.
Why simulate_deposit is rated Low
This tool only simulates/projects returns for a hypothetical deposit without actually moving any funds or modifying state. It is purely a read/calculation operation used to inform decision-making before a real deposit occurs. No financial transaction, write, or execution side effect is described.
From the tool's definition Project expected returns...Use for agent reasoning before depositing. APY is a blended target...not a guarantee.
Attacks that exploit this kind of access
The rule that runs simulate_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 simulate_deposit, this is the rule to start with:
simulate_deposit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Forge Treasury, apply this rule, and every simulate_deposit call is checked against it from then on.
Questions about simulate_deposit
Project expected returns for a USDC deposit over 30, 90, and 365 days using the blended target APY. Use for agent reasoning before depositing. APY is a blended target across conservative allocation weights; not a guarantee. Sepolia uses MockYieldAdapter until mainnet adapters are live. It is categorised as a Read tool in the Forge Treasury MCP Server, which means it retrieves data without modifying state.
simulate_deposit accepts 2 parameters: amount, profile. Required: amount. 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 simulate_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.
simulate_deposit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the simulate_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 simulate_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.
simulate_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.
This server
Across the catalogue