AI agents call list_yield_pools to retrieve information from Coin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve or enumerate yield pool information from cryptocurrency market data sources. List/query operations that return data without modifying state fall into the Read category. While the description is empty (lowering confidence slightly), the naming pattern and server context strongly suggest this is a read-only data retrieval tool with minimal blast radius if misused.
From the tool's definition Tool name 'list_yield_pools' indicates a query/list operation typical of data retrieval. Description is empty, but context from sibling tools (get_coin_details, get_coin_tickers, get_aggregated_ohlc, dex_search, get_chain_tvl_history) and server purpose…
Attacks that exploit this kind of access
list_yield_pools. It is categorised as a Read tool in the Coin MCP Server, which means it retrieves data without modifying state.
Register the Coin MCP server in PolicyLayer and add a rule for list_yield_pools: 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 Coin. Nothing to install.
list_yield_pools 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 list_yield_pools 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 list_yield_pools. 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.
list_yield_pools is provided by the Coin MCP server (sweetcornna/coin-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 →