AI agents call list_supported_exchanges 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 retrieves or queries a static list of supported exchanges with no side effects. This is consistent with other Read tools on the server (get_coin_details, get_coin_tickers, dex_search) that fetch market data. The empty description reduces confidence slightly, but the name is sufficiently clear that this is a simple data retrieval operation, not a financial transaction or destructive action.
From the tool's definition Tool name 'list_supported_exchanges' indicates a listing/retrieval operation. No description provided, but the name clearly suggests querying available exchanges rather than modifying or executing transactions.
Attacks that exploit this kind of access
list_supported_exchanges. 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_supported_exchanges: 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_supported_exchanges 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_supported_exchanges 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_supported_exchanges. 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_supported_exchanges 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 →