Get the current Lido protocol status including stake limits, withdrawal queue mode
AI agents call lido_get_protocol_status 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 simple information retrieval operation. It queries and returns the current status of the Lido protocol (stake limits, withdrawal queue mode) without side effects, state changes, or execution of external operations. This is a classic Read category operation with minimal risk—misuse would only expose existing protocol information already publicly available.
From the tool's definition Tool name 'lido_get_protocol_status' and description 'Get the current Lido protocol status including stake limits, withdrawal queue mode' indicate a read-only query operation that retrieves protocol state information without modifying or executing any actions.
Attacks that exploit this kind of access
Get the current Lido protocol status including stake limits, withdrawal queue mode. 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_protocol_status: 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_protocol_status 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_protocol_status 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_protocol_status. 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_protocol_status 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 →