find_similar_news
AI agents call find_similar_news to retrieve information from TrendRadar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'find_similar_news' clearly denotes a search/retrieval operation that queries trending news data for matches similar to a given input. No evidence of side effects, data modification, code execution, deletion, or financial impact. Despite empty description, the naming convention and server's stated purpose as an aggregation and analysis platform strongly suggest this is a read-only query tool.
From the tool's definition Tool name 'find_similar_news' and server context indicate data retrieval. Description is empty, limiting certainty. Sibling tools are all read operations (get_*, search_*, analyze_*), establishing pattern that this server performs queries without modification.
Attacks that exploit this kind of access
find_similar_news. It is categorised as a Read tool in the TrendRadar MCP Server, which means it retrieves data without modifying state.
Register the TrendRadar MCP server in PolicyLayer and add a rule for find_similar_news: 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 TrendRadar. Nothing to install.
find_similar_news 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 find_similar_news 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 find_similar_news. 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.
find_similar_news is provided by the TrendRadar MCP server (lizouzt/trendradar). 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 →