lido_lock_steth_governance · Lido MCP Server MCP

WHAT IT DOES

What lido_lock_steth_governance does on Lido MCP Server

AI agents invoke lido_lock_steth_governance to trigger actions in Lido MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why lido_lock_steth_governance needs a policy

This tool executes a blockchain transaction that locks stETH tokens into a governance escrow contract. While it doesn't permanently destroy assets, it commits tokens to a smart contract for an indeterminate period (governance veto signalling), which is a significant on-chain action with real financial implications.

From the tool's definition Lock stETH in the Lido Dual Governance veto signalling escrow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_lock_steth_governance Rate-limited

lido_lock_steth_governance stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lido_lock_steth_governance": {
      "limits": [
        {
          "counter": "lido_lock_steth_governance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lido MCP Server, so you can run agents against it safely.

FAQ

Questions about lido_lock_steth_governance

What does the lido_lock_steth_governance tool do? +

Lock stETH in the Lido Dual Governance veto signalling escrow. It is categorised as a Execute tool in the Lido MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lido_lock_steth_governance? +

Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_lock_steth_governance: 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.

What risk level is lido_lock_steth_governance? +

lido_lock_steth_governance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lido_lock_steth_governance? +

Yes. Add a rate_limit block to the lido_lock_steth_governance 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.

How do I block lido_lock_steth_governance completely? +

Set action: deny in the PolicyLayer policy for lido_lock_steth_governance. 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.

What MCP server provides lido_lock_steth_governance? +

lido_lock_steth_governance 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.