Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
AI agents call get_block_transactions 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 queries blockchain transaction data from blocks with no capability to modify, delete, or execute operations. It is a straightforward data retrieval operation with minimal blast radius if misused by an AI agent, as it cannot change state or trigger external actions. The read-only nature and querying pattern place it firmly in the Read category.
From the tool's definition Tool name 'get_block_transactions' and description 'Read-only list of transactions in a specific indexed block' explicitly indicate retrieval without side effects. The 'read-only' qualifier confirms no data modification or execution occurs.
Attacks that exploit this kind of access
Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset. 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_block_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 XGR MCP Gateway. Nothing to install.
get_block_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_block_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_block_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_block_transactions 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 →