Get transactions in a block
AI agents call getBlockTransactions to retrieve information from Somnia MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical transaction data from a blockchain block. It performs no writes, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an attacker could only gather publicly available blockchain information. Classification as 'Read' is appropriate for data retrieval operations without side effects.
From the tool's definition Tool name 'getBlockTransactions' and description 'Get transactions in a block' indicate a retrieval operation with no modification, deletion, or execution capabilities. This aligns with sibling tools (getBlockHeights, getBulkTransactions, getERC20Balance, etc.
Attacks that exploit this kind of access
Get transactions in a block. It is categorised as a Read tool in the Somnia MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Somnia MCP Server MCP server in PolicyLayer and add a rule for getBlockTransactions: 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 Somnia MCP Server. Nothing to install.
getBlockTransactions 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 getBlockTransactions 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 getBlockTransactions. 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.
getBlockTransactions is provided by the Somnia MCP Server MCP server (vastavikadi/somnia-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 →