Decode the EVM script from an Aragon vote into human-readable actions.
AI agents call lido_get_aragon_vote_script 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 and transforms existing data (EVM script decoding) for display purposes. It does not create, modify, delete, or execute any actions. It is a read-only query operation that falls squarely into the Read category. The low severity reflects minimal blast radius—misuse would only result in incorrect interpretation of vote scripts, not irreversible damage or financial impact.
From the tool's definition The tool 'lido_get_aragon_vote_script' decodes and displays an EVM script into human-readable actions. The verb 'decode' and the output-only nature (converting data into a readable format) indicate pure information retrieval with no side effects.
Attacks that exploit this kind of access
Decode the EVM script from an Aragon vote into human-readable actions. 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_aragon_vote_script: 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_aragon_vote_script 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_aragon_vote_script 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_aragon_vote_script. 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_aragon_vote_script 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 →