get_bridge_transactions
A read tool on the REI Crypto MCP server.
This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-bridge-transactions.md
What get_bridge_transactions does on REI Crypto MCP Server
AI agents call get_bridge_transactions to retrieve information from REI Crypto MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_bridge_transactions is rated Low
This tool retrieves historical bridge transaction data from cryptocurrency bridge protocols. Bridge transaction queries are informational reads with no write, execution, or financial transaction capabilities. The classification assumes standard read semantics; confidence is reduced from 0.85 to 0.75 due to the empty description, but the contextual evidence from sibling tools and server purpose is substantial.
From the tool's definition Tool name 'get_bridge_transactions' indicates retrieval of transaction data. The server is documented as providing 'API access' for 'data retrieval' without side effects.
Attacks that exploit this kind of access
The rule that runs get_bridge_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and REI Crypto MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_bridge_transactions, this is the rule to start with:
get_bridge_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect REI Crypto MCP Server, apply this rule, and every get_bridge_transactions call is checked against it from then on.
Questions about get_bridge_transactions
get_bridge_transactions is a read tool on the REI Crypto MCP Server MCP server. It is categorised as a Read tool in the REI Crypto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_bridge_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 REI Crypto MCP Server. Nothing to install.
get_bridge_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_bridge_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_bridge_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_bridge_transactions is provided by the REI Crypto MCP Server MCP server (0xreisearch/crypto-mcp-beta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on REI Crypto MCP Server, and thousands of servers like it.
This server
Across the catalogue