Get Nimiq transactions for a specific address
AI agents call get_nimiq_transactions_by_address 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 blockchain transaction data for a given address. It performs a read-only query with no side effects, no data modification, no code execution, and no financial operations. The verb 'Get' and the context of querying transaction history clearly indicate a Read category operation.
From the tool's definition Tool name contains 'get_' and description states 'Get Nimiq transactions for a specific address' — a read-only query operation that retrieves historical transaction data without modifying state.
Attacks that exploit this kind of access
Get Nimiq transactions for a specific address. 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_transactions_by_address: 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_transactions_by_address 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_transactions_by_address 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_transactions_by_address. 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_transactions_by_address 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 →