Get details of a specific transaction by its hash
AI agents call get_transaction to retrieve information from Monad MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query tool that retrieves blockchain transaction information. It does not execute transactions, modify state, delete data, or move funds. The blast radius of misuse is minimal; an attacker could only learn details about existing transactions. Classification as Read is appropriate, with low severity since it poses no destructive or financial risk.
From the tool's definition Tool name is 'get_transaction' and description states 'Get details of a specific transaction by its hash' — retrieves transaction data with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific transaction by its hash. It is categorised as a Read tool in the Monad MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Monad MCP Server MCP server in PolicyLayer and add a rule for get_transaction: 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 Monad MCP Server. Nothing to install.
get_transaction 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_transaction 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_transaction. 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_transaction is provided by the Monad MCP Server MCP server (tairon-ai/monad-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 →