Search Naver blogs for a topic. Great for finding popular content and angles.
AI agents call search_blogs 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 data from Naver blogs without creating, modifying, deleting, executing code, or committing financial transactions. It is a straightforward read operation that returns search results. The low severity reflects minimal blast radius—a misused search query can only retrieve unwanted information, not cause system damage or data loss.
From the tool's definition Tool name 'search_blogs' and description 'Search Naver blogs for a topic' indicate a query/retrieval operation with no modification or execution capabilities. The purpose is to find and retrieve existing blog content.
Attacks that exploit this kind of access
Search Naver blogs for a topic. Great for finding popular content and angles. 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 search_blogs: 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.
search_blogs 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_blogs 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_blogs. 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_blogs 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 →