get_weekly_trading_volume_by_frontend
AI agents call get_weekly_trading_volume_by_frontend 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 metrics segmented by frontend. It performs no side effects, does not execute code or commands, does not create, modify, or delete data, and does not involve financial transactions. The naming pattern and server context confirm it is a simple data query operation with read-only semantics.
From the tool's definition Tool name 'get_weekly_trading_volume_by_frontend' indicates data retrieval. Sibling tools (get_daily_trading_volume_by_dex, get_latest_trading_volume_by_aggregator, etc.) are all read-only metric queries with no mutation or execution capabilities.
Attacks that exploit this kind of access
get_weekly_trading_volume_by_frontend. 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_frontend: 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_frontend 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_frontend 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_frontend. 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_frontend 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 →