get_weekly_trading_volume_by_dex
AI agents call get_weekly_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 historical trading volume data segmented by DEX on a weekly basis. It performs no writes, deletions, code execution, or financial transactions—purely a data query operation. The low severity reflects minimal risk from misuse, as reading historical metrics poses no security or safety concern.
From the tool's definition Tool name 'get_weekly_trading_volume_by_dex' indicates retrieval of trading volume metrics. All sibling tools follow the pattern of 'get_[timeframe]_trading_volume_by_[dimension]', consistently performing data queries without modification.
Attacks that exploit this kind of access
get_weekly_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_weekly_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_weekly_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_weekly_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_weekly_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_weekly_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 →