List all staking router modules (curated, community, DVT, etc.) with their IDs and status.
AI agents call lido_get_staking_modules 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 performs a read-only operation that queries and lists information about staking router modules. It has no side effects, does not execute transactions, modify data, or consume financial resources. The blast radius of misuse is minimal—an AI agent could only retrieve public protocol information, which is a low-risk operation.
From the tool's definition Tool name 'lido_get_staking_modules' and description 'List all staking router modules' indicate a query operation that retrieves and displays data about staking modules without modifying state.
Attacks that exploit this kind of access
List all staking router modules (curated, community, DVT, etc.) with their IDs and status. 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_staking_modules: 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_staking_modules 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_staking_modules 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_staking_modules. 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_staking_modules 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 →