Create a new Lido staking vault via VaultFactory. Deploys a StakingVault and a VaultDashboard.
AI agents use lido_vault_create to create or update resources in Lido MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lido MCP Server environment.
The tool creates new smart contract instances and initializes protocol state, which are reversible writes (the vault could theoretically be destroyed or abandoned, but the deployment itself leaves permanent traces on chain and allocates resources). This is not Execute because it doesn't run arbitrary code—it calls a specific factory method.
From the tool's definition Deploys a StakingVault and a VaultDashboard via VaultFactory; this creates new contracts and establishes persistent state in the Lido protocol.
Attacks that exploit this kind of access
Create a new Lido staking vault via VaultFactory. Deploys a StakingVault and a VaultDashboard. It is categorised as a Write tool in the Lido MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_vault_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lido_vault_create 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_create. 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_create 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 →