Gets all supported liquidity sources for a specific chain.
AI agents call get_liquidity_sources to retrieve information from Odos 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 straightforward informational query that returns metadata about available liquidity sources on a blockchain. It has no ability to modify state, execute trades, transfer funds, or trigger external operations. The blast radius of misuse is minimal—an agent could only access publicly available information about which DEX liquidity providers are supported on a given chain.
From the tool's definition Tool retrieves information about supported liquidity sources with no modification capability. The verb 'gets' indicates a read-only query operation.
Attacks that exploit this kind of access
Gets all supported liquidity sources for a specific chain. It is categorised as a Read tool in the Odos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odos MCP Server MCP server in PolicyLayer and add a rule for get_liquidity_sources: 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 Odos MCP Server. Nothing to install.
get_liquidity_sources 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_liquidity_sources 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_liquidity_sources. 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_liquidity_sources is provided by the Odos MCP Server MCP server (odos-xyz/odos-mcp). 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 →