Get Nimiq transaction details by hash
AI agents call get_nimiq_transaction to retrieve information from Nimiq 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 transaction information from the Nimiq blockchain by transaction hash. It is a read-only operation that queries existing data with no side effects, no code execution, and no state changes. The low severity reflects minimal risk if misused—an agent could only retrieve publicly available blockchain transaction data.
From the tool's definition Tool name 'get_nimiq_transaction' and description 'Get Nimiq transaction details by hash' indicate a query operation that retrieves transaction data without modifying or executing any actions.
Attacks that exploit this kind of access
Get Nimiq transaction details by hash. It is categorised as a Read tool in the Nimiq MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nimiq MCP Server MCP server in PolicyLayer and add a rule for get_nimiq_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 Nimiq MCP Server. Nothing to install.
get_nimiq_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_nimiq_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_nimiq_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_nimiq_transaction is provided by the Nimiq MCP Server MCP server (onmax/nimiq-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 →