list_vaults
List all available ATV vaults. Returns vault metadata including address, chain, withdraw type, contract type, and supported deposit tokens with balances.
This record as markdown: /tools/aarna-ai-atv/list-vaults.md
What list_vaults does on Atv
AI agents call list_vaults to retrieve information from Atv 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 |
|---|---|---|---|
chain | string | — | Filter by chain name or ID (e.g. 'ethereum', 'base', '8453') |
userAddress | string | — | EVM address to include token balances for each deposit token |
Parameters from the server's own tool schema.
Why list_vaults is rated Low
This tool queries and returns vault metadata without creating, modifying, deleting, or executing any operations. It is a simple data retrieval operation typical of Read category tools. The low severity reflects that listing public vault information poses minimal risk even if misused by an agent, as it only exposes metadata without enabling transactions or state changes.
From the tool's definition Tool name 'list_vaults' and description 'List all available ATV vaults. Returns vault metadata' — purely retrieves and lists data with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs list_vaults safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Atv, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_vaults, this is the rule to start with:
list_vaults 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 Atv, apply this rule, and every list_vaults call is checked against it from then on.
Questions about list_vaults
List all available ATV vaults. Returns vault metadata including address, chain, withdraw type, contract type, and supported deposit tokens with balances. It is categorised as a Read tool in the Atv MCP Server, which means it retrieves data without modifying state.
list_vaults accepts 2 parameters: chain, userAddress. The full parameter table on this page comes from the server's own tool schema.
Register the Atv MCP server in PolicyLayer and add a rule for list_vaults: 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 Atv. Nothing to install.
list_vaults 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 list_vaults 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 list_vaults. 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.
list_vaults is provided by the Atv MCP server (aarna-ai/atv). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Atv, and thousands of servers like it.
This server
Across the catalogue