Get transaction details by hash
AI agents call get_transaction to retrieve information from Neo N3 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 blockchain transaction data by hash and returns details without modifying state, executing code, or causing side effects. It is purely informational retrieval, fitting the Read category. Severity is low because querying public blockchain data poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_transaction' and description 'Get transaction details by hash' indicate a retrieval operation with no side effects. The verb 'Get' and absence of any modification, execution, or deletion language confirm this is a read-only query.
Attacks that exploit this kind of access
Get transaction details by hash. It is categorised as a Read tool in the Neo N3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neo N3 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 Neo N3 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 Neo N3 MCP Server MCP server (r3e-network/neo-n3-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 →