get_vault_stats
Get live Forge vault TVL on Base (conservative profile in MVP). Read-only.
This record as markdown: /tools/com-forgetreasury-treasury/get-vault-stats.md
What get_vault_stats does on Forge Treasury
AI agents call get_vault_stats 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.
Why get_vault_stats is rated Low
This tool performs a data retrieval operation (querying vault statistics) with no side effects, reversibility concerns, or ability to execute code or move assets. The explicit 'Read-only' designation confirms it fits the Read category. Severity is low because exposure of vault TVL data carries minimal risk—it is typically public information about a blockchain protocol.
From the tool's definition Tool description explicitly states 'Read-only' and 'Get live Forge vault TVL on Base', which retrieves vault statistics without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_vault_stats 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 get_vault_stats, this is the rule to start with:
get_vault_stats 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 get_vault_stats call is checked against it from then on.
Questions about get_vault_stats
Get live Forge vault TVL on Base (conservative profile in MVP). Read-only. It is categorised as a Read tool in the Forge Treasury MCP Server, which means it retrieves data without modifying state.
Register the Forge Treasury MCP server in PolicyLayer and add a rule for get_vault_stats: 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.
get_vault_stats 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 get_vault_stats 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 get_vault_stats. 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.
get_vault_stats 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