get_trending_terms
AI agents call get_trending_terms to retrieve information from Google News Trends without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trending keywords/terms from Google Trends, which is a read-only query operation with no side effects. It returns data but does not create, modify, delete, or execute operations. The low severity reflects minimal blast radius if misused—an agent could only retrieve public trending data.
From the tool's definition Tool is named 'get_trending_terms' and is part of a server that 'Search and retrieve news articles and trending keywords from Google News and Google Trends.' The sibling tools use only read operations (get_news_by_keyword, get_news_by_location, etc.),…
Attacks that exploit this kind of access
get_trending_terms. It is categorised as a Read tool in the Google News Trends MCP Server, which means it retrieves data without modifying state.
Register the Google News Trends MCP server in PolicyLayer and add a rule for get_trending_terms: 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 Google News Trends. Nothing to install.
get_trending_terms 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_terms 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_terms. 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_terms is provided by the Google News Trends MCP server (jmanek/google-news-trends-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 →