get_monthly_trading_volume_by_dex
AI agents call get_monthly_trading_volume_by_dex to retrieve information from Dex Metrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trading volume metrics segmented by DEX, which is a read-only query operation with no side effects, data modification, or execution of arbitrary operations. The consistent 'get_' naming across all sibling tools and the metrics-tracking server purpose confirm this is a data retrieval function.
From the tool's definition Tool name 'get_monthly_trading_volume_by_dex' and server context indicating metrics retrieval; sibling tools all use 'get_' prefix and query trading volume data without modification or execution; description is empty but naming pattern and server purpose are…
Attacks that exploit this kind of access
get_monthly_trading_volume_by_dex. It is categorised as a Read tool in the Dex Metrics MCP Server, which means it retrieves data without modifying state.
Register the Dex Metrics MCP server in PolicyLayer and add a rule for get_monthly_trading_volume_by_dex: 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 Dex Metrics. Nothing to install.
get_monthly_trading_volume_by_dex 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_monthly_trading_volume_by_dex 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_monthly_trading_volume_by_dex. 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_monthly_trading_volume_by_dex is provided by the Dex Metrics MCP server (kukapay/dex-metrics-mcp). 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 →