AI agents call get_token_dex_price 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 retrieves price information from decentralized exchanges without modifying data, executing code, deleting resources, or moving funds. It is a passive read operation with minimal security risk. Confidence is reduced from 0.9 to 0.8 due to missing description, but the tool name and server context are sufficiently indicative.
From the tool's definition Tool name 'get_token_dex_price' indicates retrieval of DEX (decentralized exchange) price data. Sibling tools like 'get_coin_details', 'compare_prices', and 'get_aggregated_ohlc' are all data retrieval operations.
Attacks that exploit this kind of access
get_token_dex_price. 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 get_token_dex_price: 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.
get_token_dex_price 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 get_token_dex_price 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 get_token_dex_price. 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.
get_token_dex_price 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 →