aave_get_account
Reads Base Aave V3 collateral, debt, available borrowing power, LTV, and health factor for an account.
This record as markdown: /tools/awesome-base-mcp/aave-get-account.md
What aave_get_account does on Awesome Base
AI agents call aave_get_account to retrieve information from Awesome Base without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why aave_get_account is rated Low
Tool retrieves account financial data without modifying state or executing transactions.
From the tool's definition Reads Base Aave V3 collateral, debt, available borrowing power, LTV, health factor.
Attacks that exploit this kind of access
The rule that runs aave_get_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aave_get_account, this is the rule to start with:
aave_get_account 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 Awesome Base, apply this rule, and every aave_get_account call is checked against it from then on.
Questions about aave_get_account
Reads Base Aave V3 collateral, debt, available borrowing power, LTV, and health factor for an account. It is categorised as a Read tool in the Awesome Base MCP Server, which means it retrieves data without modifying state.
Register the Awesome Base MCP server in PolicyLayer and add a rule for aave_get_account: 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 Awesome Base. Nothing to install.
aave_get_account 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 aave_get_account 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 aave_get_account. 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.
aave_get_account is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Awesome Base, and thousands of servers like it.
This server
Across the catalogue