search_related_news_history
AI agents call search_related_news_history 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.
This tool searches and retrieves news history records. It has no side effects, creates no data, executes no code, deletes nothing, and involves no financial operations. Despite the empty description, the contextual evidence from the tool name and sibling tools confirms it is a Read operation with low severity and blast radius.
From the tool's definition Tool name 'search_related_news_history' indicates a search/query operation. The description is empty, but the sibling tools on this server (get_latest_news, get_news_by_date, find_similar_news, analyze_data_insights) are all read-only data retrieval…
Attacks that exploit this kind of access
search_related_news_history. 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 search_related_news_history: 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.
search_related_news_history 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 search_related_news_history 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 search_related_news_history. 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.
search_related_news_history is provided by the TrendRadar MCP server (yanglang116/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 →