AI agents call list_latest_dex_tokens 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 name strongly suggests it retrieves or lists recent tokens from decentralized exchanges without modifying, executing, or deleting anything. The empty description reduces confidence slightly, but the naming convention and context from sibling tools (all read-category operations) indicate this is a data retrieval tool with no side effects. Blast radius is minimal—returns market data only.
From the tool's definition Tool name 'list_latest_dex_tokens' indicates a listing/retrieval operation on DEX token data. No description provided, but sibling tools like 'dex_search', 'get_coin_details', and 'get_coin_tickers' are all query/retrieval operations, suggesting this tool…
Attacks that exploit this kind of access
list_latest_dex_tokens. 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_latest_dex_tokens: 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_latest_dex_tokens 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_latest_dex_tokens 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_latest_dex_tokens. 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_latest_dex_tokens 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 →