Timeline for an Aragon vote: start time, main phase end, objection phase end,
AI agents call lido_get_aragon_vote_timeline 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 is a pure query tool that fetches temporal information about governance votes. It has no ability to modify state, execute transactions, move funds, or delete data. The blast radius if misused by an AI agent is minimal—at worst providing outdated or incorrect governance information for decision-making, but not causing financial loss or irreversible changes.
From the tool's definition Tool retrieves vote timeline data (start time, main phase end, objection phase end) with no modification or execution capability. Name contains 'get' and description indicates data retrieval only.
Attacks that exploit this kind of access
Timeline for an Aragon vote: start time, main phase end, objection phase end,. 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_timeline: 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_timeline 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_timeline 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_timeline. 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_timeline 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 →