Get logs for transaction created by the provided address
AI agents call getTransactionLogsForAddress 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 queries historical blockchain transaction data without any ability to modify state, execute code, or transfer funds. It is purely informational retrieval from the ORMI API. The blast radius of misuse is minimal—an attacker could enumerate transaction history but cannot alter balances, execute transactions, or cause financial harm.
From the tool's definition Tool retrieves transaction logs for a given address; description uses 'Get logs' which indicates data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get logs for transaction created by the provided address. 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 getTransactionLogsForAddress: 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.
getTransactionLogsForAddress 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 getTransactionLogsForAddress 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 getTransactionLogsForAddress. 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.
getTransactionLogsForAddress 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 →