get_historical_nav
Get historical NAV (Net Asset Value) data points for an ATV vault over a specified number of days. Useful for charting price trends.
This record as markdown: /tools/aarna-ai-atv/get-historical-nav.md
What get_historical_nav does on Atv
AI agents call get_historical_nav 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 |
|---|---|---|---|
days | string | — | Number of days of history to return (default: 30) |
address | string | — | Vault contract address |
Parameters from the server's own tool schema.
Why get_historical_nav is rated Low
This tool retrieves and queries historical Net Asset Value metrics for charting and analysis purposes. It has no side effects, does not modify data, execute code, delete data, or move funds. The action is purely informational retrieval, fitting the 'Read' category with low severity risk.
From the tool's definition Tool name 'get_historical_nav' and description 'Get historical NAV (Net Asset Value) data points for an ATV vault over a specified number of days' indicates retrieval of historical data with no modification or execution of transactions.
Attacks that exploit this kind of access
The rule that runs get_historical_nav 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_historical_nav, this is the rule to start with:
get_historical_nav 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_historical_nav call is checked against it from then on.
Questions about get_historical_nav
Get historical NAV (Net Asset Value) data points for an ATV vault over a specified number of days. Useful for charting price trends. It is categorised as a Read tool in the Atv MCP Server, which means it retrieves data without modifying state.
get_historical_nav accepts 2 parameters: days, 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_historical_nav: 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_historical_nav 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_historical_nav 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_historical_nav. 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_historical_nav 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