Use this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available.
AI agents call get_transaction_evidence to retrieve information from XGR MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transaction evidence and status information from blockchain explorers and RPC nodes. It performs a read-only query operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal since it only exposes historical transaction data already publicly available on-chain.
From the tool's definition Tool description states it 'Combines indexed Explorer transaction data, receipt data and live RPC fallback if available' — purely retrieves and queries historical transaction information with no capability to modify, execute, or delete data.
Attacks that exploit this kind of access
Use this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available. It is categorised as a Read tool in the XGR MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the XGR MCP Gateway MCP server in PolicyLayer and add a rule for get_transaction_evidence: 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 XGR MCP Gateway. Nothing to install.
get_transaction_evidence 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_transaction_evidence 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_transaction_evidence. 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_transaction_evidence is provided by the XGR MCP Gateway MCP server (xgr-network/xgr-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 →