get_day_stats
AI agents call get_day_stats 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 retrieves or queries statistical data about daily metrics from a blockchain bridge analytics service. It fits the Read category: data retrieval with no side effects. The empty description reduces confidence slightly, but the naming pattern and sibling tools (all get/list operations) strongly suggest read-only analytics querying.
From the tool's definition Tool name 'get_day_stats' and sibling tools (get_historical_volumes, get_transactions, list_bridges, list_chains) are all read-only retrieval operations.
Attacks that exploit this kind of access
get_day_stats. 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_day_stats: 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_day_stats 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_day_stats 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_day_stats. 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_day_stats 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 →