Check the token allowance for a spender address. Shows how much of your stETH/wstETH/LDO
AI agents call lido_get_allowance 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 queries blockchain state to retrieve the current token allowance granted to a spender, which is a read operation with no side effects. It does not create, modify, delete, or execute any transactions. The blast radius of misuse is minimal—an attacker could only learn what allowances exist, not modify them or move funds.
From the tool's definition Tool name 'lido_get_allowance' and description 'Check the token allowance for a spender address. Shows how much of your stETH/wstETH/LDO' indicate a read-only query operation that retrieves allowance information without modifying state.
Attacks that exploit this kind of access
Check the token allowance for a spender address. Shows how much of your stETH/wstETH/LDO. 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_allowance: 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_allowance 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_allowance 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_allowance. 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_allowance 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 →