Get account information including address and balances across all chains.
AI agents call get_account_info to retrieve information from Paloma DEX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays existing data about an account. It does not modify, execute, delete, or move funds. While it operates in a financial context (Paloma DEX), the tool itself performs no financial transactions or state changes. The blast radius of misuse is minimal — an attacker gaining access would only expose read-only account information, not execute trades or drain funds.
From the tool's definition Tool name is 'get_account_info' and description states it retrieves 'account information including address and balances across all chains' — purely a query operation with no side effects.
Attacks that exploit this kind of access
Get account information including address and balances across all chains. It is categorised as a Read tool in the Paloma DEX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Paloma DEX MCP Server MCP server in PolicyLayer and add a rule for get_account_info: 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 Paloma DEX MCP Server. Nothing to install.
get_account_info 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_account_info 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_account_info. 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_account_info is provided by the Paloma DEX MCP Server MCP server (volumefi/mcppadex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →