Get PUSD token balance on specified chain.
AI agents call get_pusd_balance 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 retrieves balance information without modifying, executing, or affecting any state. Despite the server's overall capability to execute financial transactions, this specific tool is a simple query that fetches account balance data. It poses minimal risk as it cannot be misused to cause harm—at worst, an agent learns a user's balance. Classified as Read with low severity.
From the tool's definition Tool name is 'get_pusd_balance' and description states 'Get PUSD token balance on specified chain.' The verb 'Get' indicates a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get PUSD token balance on specified chain. 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_pusd_balance: 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_pusd_balance 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_pusd_balance 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_pusd_balance. 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_pusd_balance 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 →