This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-tx.md
What get_tx does on REI Crypto MCP Server
AI agents call get_tx 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_tx is rated Low
This tool retrieves transaction data from a blockchain, which is a read operation with no side effects. Severity is medium rather than low because transaction details could expose sensitive financial information (amounts, addresses, counterparties) that could be misused for targeting, surveillance, or social engineering if an AI agent overexposed them without proper filtering.
From the tool's definition Tool name 'get_tx' with description 'GET /tx/{hash}' retrieves a single transaction by hash. This is a read-only query operation that returns data without modification or execution. The GET HTTP method and path structure confirm retrieval semantics.
Attacks that exploit this kind of access
The rule that runs get_tx 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_tx, this is the rule to start with:
get_tx 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_tx call is checked against it from then on.
Questions about get_tx
GET /tx/{hash}. 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_tx: 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_tx 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_tx 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_tx. 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_tx 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