get_withdraw_status
Check whether withdrawals are currently paused on an ATV vault. Use this before building a withdraw transaction.
This record as markdown: /tools/aarna-ai-atv/get-withdraw-status.md
What get_withdraw_status does on Atv
AI agents call get_withdraw_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_withdraw_status is rated Low
This tool retrieves the current pause status of withdrawals on a vault—a read-only operation with no side effects. It is informational only and is explicitly described as a check to be performed before building a transaction, not the transaction itself. No data is created, modified, deleted, or financial movement is initiated.
From the tool's definition Tool name 'get_withdraw_status' and description 'Check whether withdrawals are currently paused on an ATV vault' indicates a query operation that retrieves status information without modifying or executing transactions.
Attacks that exploit this kind of access
The rule that runs get_withdraw_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_withdraw_status, this is the rule to start with:
get_withdraw_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_withdraw_status call is checked against it from then on.
Questions about get_withdraw_status
Check whether withdrawals are currently paused on an ATV vault. Use this before building a withdraw transaction. It is categorised as a Read tool in the Atv MCP Server, which means it retrieves data without modifying state.
get_withdraw_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_withdraw_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_withdraw_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_withdraw_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_withdraw_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_withdraw_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