Get Nimiq validator information by address
AI agents call get_nimiq_validator 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 information about a validator on the Nimiq blockchain given an address. It performs a simple lookup/query with no side effects—no data is created, modified, deleted, or financial transactions are initiated. The operation is purely informational, consistent with other Read tools on this server like get_nimiq_account, get_nimiq_balance, and get_nimiq_block_by_hash.
From the tool's definition Tool name 'get_nimiq_validator' and description 'Get Nimiq validator information by address' indicate a read-only query operation that retrieves validator data from the blockchain without modifying state.
Attacks that exploit this kind of access
Get Nimiq validator information by 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_validator: 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_validator 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_validator 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_validator. 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_validator 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 →