get_transactions
AI agents call get_transactions 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.
The tool appears to retrieve transaction data from blockchain bridges for analytical purposes. The naming pattern 'get_' is consistent with read operations, and the server's stated purpose is to provide metrics and enable analysis rather than modify state.
From the tool's definition Tool name 'get_transactions' and server description indicating 'analyze liquidity, transaction flows, and performance across blockchain networks' suggest data retrieval. No description provided for the tool itself.
Attacks that exploit this kind of access
get_transactions. 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_transactions: 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_transactions 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_transactions 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_transactions. 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_transactions 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 →