Get logs from blocks
AI agents call getTransactionLogs 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 transaction logs from blocks, which is a read-only operation that queries existing blockchain data without creating, modifying, executing code, deleting data, or moving funds. The blast radius of misuse is minimal—at worst, an agent could query logs repeatedly or access sensitive transaction data, but no irreversible actions or state changes are possible.
From the tool's definition Tool name 'getTransactionLogs' and description 'Get logs from blocks' indicate data retrieval with no modification. The Somnia MCP Server description confirms this tool is for 'retrieve[ing]...transaction history' through read-only blockchain queries.
Attacks that exploit this kind of access
Get logs from blocks. 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 getTransactionLogs: 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.
getTransactionLogs 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 getTransactionLogs 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 getTransactionLogs. 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.
getTransactionLogs 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 →