Burn stETH shares to reduce a vault
AI agents call lido_vault_burn_shares to permanently remove resources in Lido MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Burning shares is an irreversible destructive operation - once stETH shares are burned, they cannot be recovered. This permanently reduces the vault's position and destroys the burned tokens, making it a Destructive category with high severity due to the potential for significant financial loss if misused.
From the tool's definition Burn stETH shares to reduce a vault
Attacks that exploit this kind of access
Burn stETH shares to reduce a vault. It is categorised as a Destructive tool in the Lido MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_vault_burn_shares: 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_vault_burn_shares is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the lido_vault_burn_shares 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_vault_burn_shares. 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_vault_burn_shares 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 →