get_historical_volumes
AI agents call get_historical_volumes to retrieve information from Bridge Metrics MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve historical volume data from bridge metrics without modifying state, executing code, or causing financial transactions. The naming pattern and server purpose suggest analytics and querying only. While the description is empty, the tool name and context strongly indicate a read operation with minimal risk.
From the tool's definition Tool name 'get_historical_volumes' indicates data retrieval with no mutation capability. Server context describes 'real-time cross-chain bridge metrics' and 'analyze liquidity, transaction flows' — all read operations.
Attacks that exploit this kind of access
get_historical_volumes. It is categorised as a Read tool in the Bridge Metrics MCP MCP Server, which means it retrieves data without modifying state.
Register the Bridge Metrics MCP server in PolicyLayer and add a rule for get_historical_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 Bridge Metrics MCP. Nothing to install.
get_historical_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_historical_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_historical_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_historical_volumes is provided by the Bridge Metrics MCP server (kukapay/bridge-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 →