AI agents call get_trending_coins to retrieve information from Portfolio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context of a portfolio analysis server indicate this retrieves cryptocurrency trend data without modifying state. Although the description is empty, reducing confidence slightly, the tool does not create, modify, delete, execute code, or move money. It is a read operation retrieving financial market data, typical of portfolio analysis workflows.
From the tool's definition Tool name 'get_trending_coins' suggests data retrieval from CoinGecko; server description mentions fetching financial data from CoinGecko; no description provided, but naming convention aligns with read-only operations (get_*).
Attacks that exploit this kind of access
get_trending_coins. It is categorised as a Read tool in the Portfolio MCP Server, which means it retrieves data without modifying state.
Register the Portfolio MCP server in PolicyLayer and add a rule for get_trending_coins: 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 Portfolio. Nothing to install.
get_trending_coins 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_coins 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_coins. 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_coins is provided by the Portfolio MCP server (l4b4r4b4b4/portfolio-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 →