Estimate how long a withdrawal will take to finalize.
AI agents call lido_estimate_withdrawal_time 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 information about withdrawal timing without creating, modifying, deleting, or executing any transactions. It is purely informational and read-only, making it a Read category risk with low severity since estimation errors have minimal security impact.
From the tool's definition Tool name contains 'estimate' and description states it provides time estimation ('how long a withdrawal will take to finalize'), indicating a query operation with no side effects or state modifications.
Attacks that exploit this kind of access
Estimate how long a withdrawal will take to finalize. 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_estimate_withdrawal_time: 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_estimate_withdrawal_time 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_estimate_withdrawal_time 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_estimate_withdrawal_time. 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_estimate_withdrawal_time 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 →