AI agents call get_trending 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 appears to query and retrieve trending market data from the server's data sources. No modification, deletion, execution, or financial transaction occurs—it simply fetches information. The empty description lowers confidence slightly, but the server's stated purpose (enabling LLMs to answer market questions) and the clear Read-category pattern of sibling tools support this classification.
From the tool's definition Tool named 'get_trending' on a 'cryptocurrency market-data MCP server' with sibling tools like 'get_coin_details', 'get_coin_tickers', and 'compare_prices' that are clearly data retrieval operations.
Attacks that exploit this kind of access
get_trending. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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 →