lido_vote_on_proposal · Lido MCP Server MCP: Risk & Policy

WHAT IT DOES

What lido_vote_on_proposal does on Lido MCP Server

AI agents invoke lido_vote_on_proposal 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_vote_on_proposal needs a policy

This tool submits an on-chain governance vote to the Lido DAO, triggering an external blockchain transaction. It's an Execute-category action because it performs an irreversible on-chain operation (voting) with real protocol governance consequences. While not directly financial or destructive of data, governance votes can approve protocol changes affecting large amounts of staked ETH, making misuse high severity.

From the tool's definition Cast a vote on a Lido DAO Aragon governance proposal

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_vote_on_proposal Rate-limited

lido_vote_on_proposal 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_vote_on_proposal": {
      "limits": [
        {
          "counter": "lido_vote_on_proposal_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_vote_on_proposal

What does the lido_vote_on_proposal tool do? +

Cast a vote on a Lido DAO Aragon governance proposal. 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_vote_on_proposal? +

Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_vote_on_proposal: 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_vote_on_proposal? +

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

Can I rate-limit lido_vote_on_proposal? +

Yes. Add a rate_limit block to the lido_vote_on_proposal 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_vote_on_proposal completely? +

Set action: deny in the PolicyLayer policy for lido_vote_on_proposal. 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_vote_on_proposal? +

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