Add an alert rule to a watched vault. Rules use mathjs expressions evaluated against
AI agents use lido_add_rule 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.
This tool writes/creates new data (alert rules) in a watched vault configuration without permanently destroying data or moving financial assets. While it affects monitoring behavior, the action is not inherently destructive or financial.
From the tool's definition Tool name 'lido_add_rule' and description indicate creation of alert rules ('Add an alert rule'). The action is reversible (rules can be modified or deleted) and creates new configuration state.
Attacks that exploit this kind of access
Add an alert rule to a watched vault. Rules use mathjs expressions evaluated against. 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_add_rule: 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_add_rule 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_add_rule 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_add_rule. 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_add_rule 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 →