AI agents call list_stablecoins 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.
This tool queries cryptocurrency market data and returns a list without modifying, deleting, or executing operations. The 'list_' prefix is a standard naming convention for read-only retrieval operations. While the description is empty, the name and context of sibling tools strongly indicate it retrieves stablecoin data only, making it a Read category tool with low severity impact.
From the tool's definition Tool name 'list_stablecoins' indicates a retrieval operation that returns a list of stablecoins. The sibling tools on this server (cache_stats, get_coin_details, get_coin_tickers, dex_search, get_aggregated_ohlc) are all data retrieval operations with no side…
Attacks that exploit this kind of access
list_stablecoins. 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_stablecoins: 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_stablecoins 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_stablecoins 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_stablecoins. 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_stablecoins 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 →