lido_vault_pause_beacon_deposits · Lido MCP Server MCP

WHAT IT DOES

What lido_vault_pause_beacon_deposits does on Lido MCP Server

AI agents invoke lido_vault_pause_beacon_deposits 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_vault_pause_beacon_deposits needs a policy

This tool triggers an operational state change on a staking vault by pausing beacon chain deposits. While not permanently destructive (it's reversible in principle), it executes an external blockchain transaction that halts deposit functionality, which can significantly impact staking operations and yield. It falls under Execute as it triggers an external operation with real protocol-level effects.

From the tool's definition Pause beacon chain deposits for a staking vault

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_vault_pause_beacon_deposits Rate-limited

lido_vault_pause_beacon_deposits 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_vault_pause_beacon_deposits": {
      "limits": [
        {
          "counter": "lido_vault_pause_beacon_deposits_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_vault_pause_beacon_deposits

What does the lido_vault_pause_beacon_deposits tool do? +

Pause beacon chain deposits for a staking vault. 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_vault_pause_beacon_deposits? +

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

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

Can I rate-limit lido_vault_pause_beacon_deposits? +

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

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

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