List node operators in the curated staking module. Shows operator name, reward address,
AI agents call lido_get_node_operators to retrieve information from Lido 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 and displays public information about node operators (name, reward address, etc.) with no side effects. It is a simple data query operation that does not create, modify, delete, or execute any transactions or code. The read-only nature and absence of destructive or financial operations place it squarely in the Read category with low severity.
From the tool's definition Tool name 'lido_get_node_operators' and description 'List node operators in the curated staking module' indicate a query/retrieval operation that returns information about node operators without modifying state.
Attacks that exploit this kind of access
List node operators in the curated staking module. Shows operator name, reward address,. It is categorised as a Read tool in the Lido MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_get_node_operators: 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 Lido MCP Server. Nothing to install.
lido_get_node_operators 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 lido_get_node_operators 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 lido_get_node_operators. 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.
lido_get_node_operators is provided by the Lido MCP Server MCP server (the-wunmi/lido-mcp-server). 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 →