LIVE on-chain read of a user's Aave V3 account state via Pool.getUserAccountData. Returns current-block health factor, total collateral/debt (base units, 8 decimals), available borrows, current liquidation threshold, and LTV. Use this BEFORE reporting any 'critical' or 'liquidatable' position fro...
Part of the Graph Aave server.
Free to start. No card required.
AI agents call get_live_user_account_data to retrieve information from Graph Aave without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_live_user_account_data only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_live_user_account_data": {}
}
}See the full Graph Aave policy for all 46 tools.
These attack patterns abuse exactly the kind of access get_live_user_account_data gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
LIVE on-chain read of a user's Aave V3 account state via Pool.getUserAccountData. Returns current-block health factor, total collateral/debt (base units, 8 decimals), available borrows, current liquidation threshold, and LTV. Use this BEFORE reporting any 'critical' or 'liquidatable' position from subgraph data — subgraphs lag chainhead by N blocks and a position rated CRITICAL in the index may already be liquidated (or no longer at risk). Response includes as_of.block so freshness survives context compaction.. It is categorised as a Read tool in the Graph Aave MCP Server, which means it retrieves data without modifying state.
Register the Graph Aave MCP server in PolicyLayer and add a rule for get_live_user_account_data: 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 Graph Aave. Nothing to install.
get_live_user_account_data 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_live_user_account_data 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_live_user_account_data. 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_live_user_account_data is provided by the Graph Aave MCP server (graph-aave-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 Graph Aave tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.