Get a Nimiq block by its hash
AI agents call get_nimiq_block_by_hash 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 immutable blockchain data (a block record identified by hash) with no side effects, no code execution, and no data modification. It is a straightforward read operation on a distributed ledger. The low severity reflects minimal blast radius: even if an AI agent repeatedly queries blocks, no financial, operational, or destructive harm occurs.
From the tool's definition Tool description states 'Get a Nimiq block by its hash' — this retrieves blockchain block data without modifying or executing anything. The verb 'get' and read-only nature of querying historical block data by hash confirms this is a query operation.
Attacks that exploit this kind of access
Get a Nimiq block by its 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_block_by_hash: 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_block_by_hash 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_block_by_hash 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_block_by_hash. 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_block_by_hash 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 →