Check the current owner of a withdrawal request NFT by request ID.
AI agents call lido_get_withdrawal_nft_owner 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 queries data (withdrawal NFT owner details) with no side effects on blockchain state, balances, or operations. It is a straightforward lookup operation and falls squarely into the Read category. The severity is low because misuse cannot cause financial loss, data destruction, or unauthorized state changes—it only exposes existing ownership information.
From the tool's definition Tool name 'lido_get_withdrawal_nft_owner' and description 'Check the current owner of a withdrawal request NFT by request ID' indicate a query operation that retrieves ownership information without modifying state or triggering transactions.
Attacks that exploit this kind of access
Check the current owner of a withdrawal request NFT by request ID. 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_withdrawal_nft_owner: 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_withdrawal_nft_owner 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_withdrawal_nft_owner 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_withdrawal_nft_owner. 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_withdrawal_nft_owner 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 →