Analyze Naver search trends for given keywords.
AI agents call trend_keywords to retrieve information from Content Research without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes publicly available trend data from Naver DataLab. It does not create, modify, delete, or execute any operations—it simply queries and presents existing trend information. This is a straightforward data retrieval operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'trend_keywords' combined with description 'Analyze Naver search trends for given keywords' indicates querying and analyzing existing trend data. The verb 'analyze' applied to search trends is a read operation with no side effects on data.
Attacks that exploit this kind of access
Analyze Naver search trends for given keywords. It is categorised as a Read tool in the Content Research MCP Server, which means it retrieves data without modifying state.
Register the Content Research MCP server in PolicyLayer and add a rule for trend_keywords: 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 Content Research. Nothing to install.
trend_keywords 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 trend_keywords 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 trend_keywords. 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.
trend_keywords is provided by the Content Research MCP server (wjddusrb03/content-research-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 →