Get a single transaction by its hash
AI agents call getOneTransaction 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 or queries data from the blockchain (a specific transaction by hash) with no side effects, state changes, or ability to modify, delete, or execute operations. It is purely informational, consistent with other Read-category tools on the same server (getBlockHeights, getBlockTransactions, getERC20Balance, etc.).
From the tool's definition Tool name 'getOneTransaction' and description 'Get a single transaction by its hash' indicate a read-only query operation that retrieves existing blockchain transaction data without modification, deletion, or execution.
Attacks that exploit this kind of access
Get a single transaction by its hash. 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 getOneTransaction: 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.
getOneTransaction 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 getOneTransaction 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 getOneTransaction. 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.
getOneTransaction 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 →