Get trending normalized feeds for hot or popular crypto news.
AI agents call get_trending_feeds to retrieve information from Followin MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries trending cryptocurrency news and feeds from the Followin platform. It performs a read-only operation to fetch existing data without side effects such as creation, modification, deletion, or execution of external operations. The data returned is informational content about crypto trends and news, posing minimal security risk.
From the tool's definition Tool name 'get_trending_feeds' and description 'Get trending normalized feeds for hot or popular crypto news' indicate data retrieval with no modification, deletion, or code execution capabilities.
Attacks that exploit this kind of access
Get trending normalized feeds for hot or popular crypto news. It is categorised as a Read tool in the Followin MCP MCP Server, which means it retrieves data without modifying state.
Register the Followin MCP server in PolicyLayer and add a rule for get_trending_feeds: 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 Followin MCP. Nothing to install.
get_trending_feeds 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_feeds 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_feeds. 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_feeds is provided by the Followin MCP server (qinshoudawang/crypto-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 →