Returns votes for a specific governance proposal
AI agents call get-proposal-votes to retrieve information from Osmosis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of governance voting data. It retrieves information about votes cast on a proposal but does not create, modify, delete, or execute any transactions. The action is passive data retrieval with no side effects, fitting the Read category. Severity is low because access to public governance voting data poses minimal risk even if an AI agent queries it without restriction.
From the tool's definition Tool name 'get-proposal-votes' and description 'Returns votes for a specific governance proposal' indicate a query operation that retrieves and displays existing data without modifying state.
Attacks that exploit this kind of access
Returns votes for a specific governance proposal. It is categorised as a Read tool in the Osmosis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Osmosis MCP Server MCP server in PolicyLayer and add a rule for get-proposal-votes: 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 Osmosis MCP Server. Nothing to install.
get-proposal-votes 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 get-proposal-votes 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 get-proposal-votes. 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.
get-proposal-votes is provided by the Osmosis MCP Server MCP server (myronkoch-dev/mcp-osmosis). 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 →