get_lending_positions
Fetch all Aave V3 lending/borrowing positions for a wallet. Returns collateral, debt (both in USD and per-asset), health factor, LTV, and liquidation threshold across Ethereum and Arbitrum.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-lending-positions.md
What get_lending_positions does on VaultPilot MCP
AI agents call get_lending_positions to retrieve information from VaultPilot MCP 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 |
|---|---|---|---|
chains | array | — | |
wallet | string | Yes |
Parameters from the server's own tool schema.
Why get_lending_positions is rated Low
This tool retrieves and returns information about existing lending positions. It performs a read-only query against Aave V3 smart contracts, analogous to checking account balances or portfolio status. There are no side effects, no money movement, no code execution, and no data modification. The information returned could inform financial decisions, but the tool itself only reads data.
From the tool's definition Tool name and description both indicate a fetch/query operation: 'Fetch all Aave V3 lending/borrowing positions'. Returns data (collateral, debt, health factor, LTV, liquidation threshold) with no mention of modifications, transactions, or state changes.
Attacks that exploit this kind of access
The rule that runs get_lending_positions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_lending_positions, this is the rule to start with:
get_lending_positions 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 VaultPilot MCP, apply this rule, and every get_lending_positions call is checked against it from then on.
Questions about get_lending_positions
Fetch all Aave V3 lending/borrowing positions for a wallet. Returns collateral, debt (both in USD and per-asset), health factor, LTV, and liquidation threshold across Ethereum and Arbitrum. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.
get_lending_positions accepts 2 parameters: chains, wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for get_lending_positions: 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 VaultPilot MCP. Nothing to install.
get_lending_positions 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_lending_positions 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_lending_positions. 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_lending_positions is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
This server
Across the catalogue