get_transaction
Get detailed information about a specific transaction by its hash. Includes sender, recipient, value, data, and more.
This record as markdown: /tools/chulanpro5-evm-mcp-server/get-transaction.md
What get_transaction does on EVM MCP Server
AI agents call get_transaction to retrieve information from EVM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_transaction is rated Low
This tool retrieves blockchain transaction details by hash—a purely informational operation with no side effects. It matches the 'Read' category definition: retrieves or queries data with no state modifications. Severity is low because accessing publicly available blockchain transaction data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_transaction' and description 'Get detailed information about a specific transaction by its hash' indicate a query operation that retrieves transaction data without modifying state or triggering external actions.
Attacks that exploit this kind of access
The rule that runs get_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_transaction, this is the rule to start with:
get_transaction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every get_transaction call is checked against it from then on.
Questions about get_transaction
Get detailed information about a specific transaction by its hash. Includes sender, recipient, value, data, and more. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM 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 EVM 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 EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EVM MCP Server, and thousands of servers like it.
This server
Across the catalogue