get_deposit_status
Check whether deposits are currently paused on an ATV vault. Use this before building a deposit transaction to avoid sending a doomed tx.
This record as markdown: /tools/aarna-ai-atv/get-deposit-status.md
What get_deposit_status does on Atv
AI agents call get_deposit_status 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 |
Parameters from the server's own tool schema.
Why get_deposit_status is rated Low
This tool retrieves the pause status of vault deposits—a read-only query operation. It has no capacity to modify data, execute code, or incur financial obligations. The purpose is informational only, to help avoid failed transactions. Even in a misuse scenario, an AI agent can only read vault status, causing no harm. Severity is low because there is no blast radius from reading this data.
From the tool's definition Tool name is 'get_deposit_status' and description states it 'Check[s] whether deposits are currently paused on an ATV vault.' This is a query operation that retrieves state information with no side effects.
Attacks that exploit this kind of access
The rule that runs get_deposit_status 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_deposit_status, this is the rule to start with:
get_deposit_status 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_deposit_status call is checked against it from then on.
Questions about get_deposit_status
Check whether deposits are currently paused on an ATV vault. Use this before building a deposit transaction to avoid sending a doomed tx. It is categorised as a Read tool in the Atv MCP Server, which means it retrieves data without modifying state.
get_deposit_status accepts 1 parameter: address. 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_deposit_status: 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_deposit_status 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_deposit_status 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_deposit_status. 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_deposit_status 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