get_vault
Get metadata for a specific ATV vault by its contract address.
This record as markdown: /tools/aarna-ai-atv/get-vault.md
What get_vault does on Atv
AI agents call get_vault 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 |
|---|---|---|---|
address | string | — | Vault contract address |
userAddress | string | — | EVM address to include token balances for |
Parameters from the server's own tool schema.
Why get_vault is rated Low
This tool retrieves and returns vault metadata by contract address. It performs a query operation that does not modify state, execute code, delete data, or move funds. The 'get' operation is explicitly a read action.
From the tool's definition Tool name 'get_vault' and description 'Get metadata for a specific ATV vault' indicate a retrieval operation. The verb 'get' and 'metadata' retrieval are characteristic of read-only queries with no side effects.
Attacks that exploit this kind of access
The rule that runs get_vault 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 get_vault, this is the rule to start with:
get_vault 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 get_vault call is checked against it from then on.
Questions about get_vault
Get metadata for a specific ATV vault by its contract address. It is categorised as a Read tool in the Atv MCP Server, which means it retrieves data without modifying state.
get_vault accepts 2 parameters: address, 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 get_vault: 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.
get_vault 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 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. 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 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