AI agents call get_dex_volumes to retrieve information from MoltLlama without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves historical and current DEX volume metrics from DeFiLlama. It performs a read-only query operation with no side effects, no code execution, no data modification, and no financial transactions. The blast radius of misuse is minimal—an AI agent cannot cause damage by requesting volume data.
From the tool's definition Tool description states it 'Get[s] DEX volume overview and per-protocol volumes' with 'volume data and historical chart' — purely retrieves and queries blockchain data with no modification, deletion, execution, or financial transaction capabilities.
Attacks that exploit this kind of access
Get DEX volume overview and per-protocol volumes. Returns top 100 DEXs with 24h/7d/30d volume data and historical chart. It is categorised as a Read tool in the MoltLlama MCP Server, which means it retrieves data without modifying state.
Register the MoltLlama MCP server in PolicyLayer and add a rule for get_dex_volumes: 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 MoltLlama. Nothing to install.
get_dex_volumes 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_dex_volumes 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_dex_volumes. 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_dex_volumes is provided by the MoltLlama MCP server (moltllama/moltllama). 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 →