AI agents call compare_prices 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 and compare price information across cryptocurrency markets or sources. This is a read-only query operation with no side effects, data modification, execution of external code, or financial transactions. The lack of side-effect-causing language ('create', 'delete', 'execute', 'trade') and alignment with similar data-retrieval tools on the server supports Read classification.
From the tool's definition Tool name 'compare_prices' and server context (cryptocurrency market-data MCP) indicate data retrieval. No description provided, but sibling tools like 'get_coin_tickers', 'get_coin_details', and 'get_aggregated_ohlc' are all Read operations that query market…
Attacks that exploit this kind of access
compare_prices. 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 compare_prices: 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.
compare_prices 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 compare_prices 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 compare_prices. 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.
compare_prices 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 →