Returns the current spot price between two tokens in a pool
AI agents call get-pool-spot-price 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 data retrieval only (Read category). It queries existing blockchain state to return pricing information with no side effects, no asset transfers, and no state mutations. Even in the context of a blockchain interaction server, a spot price query is a safe read operation. Severity is low due to minimal blast radius—incorrect pricing data affects only decision-making, not funds.
From the tool's definition Tool description states it 'Returns the current spot price between two tokens in a pool' - this is a query operation that retrieves data without modifying state or executing transactions.
Attacks that exploit this kind of access
Returns the current spot price between two tokens in a pool. 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-pool-spot-price: 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-pool-spot-price 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-pool-spot-price 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-pool-spot-price. 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-pool-spot-price 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 →