Get cross-system governance power for an address:
AI agents call lido_get_voting_power to retrieve information from Lido MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves voting power data for a given address—a pure read operation with no side effects. It does not modify data, execute code, transfer funds, or trigger external operations. The action is informational only, making it a Read category tool with low severity since unauthorized access to voting power information poses minimal risk compared to tools that can execute transactions or modify positions.
From the tool's definition Tool name 'lido_get_voting_power' and description 'Get cross-system governance power for an address' indicate a query operation that retrieves governance information without modifying state or executing transactions.
Attacks that exploit this kind of access
Get cross-system governance power for an address:. It is categorised as a Read tool in the Lido MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_get_voting_power: 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_get_voting_power is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lido_get_voting_power 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_get_voting_power. 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_get_voting_power 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 →