✍️ Search personal blogs and reviews for authentic user experiences. Great for product reviews, personal stories, detailed tutorials, and real user opinions. Find genuine Korean perspectives. For recent posts or
AI agents call search_blog to retrieve information from Naver Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available blog content and reviews without creating, modifying, deleting, or executing any operations. It is a straightforward Read operation with minimal security risk. The low severity reflects that misuse would only expose or aggregate publicly searchable information, not compromise systems or data integrity.
From the tool's definition Tool name 'search_blog' and description explicitly states it 'Search[es] personal blogs and reviews' — a retrieval operation with no modification or execution capability.
Documented attack patterns abuse exactly the kind of access search_blog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Naver Search MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_blog:
{
"version": "1",
"default": "deny",
"tools": {
"search_blog": {}
}
}search_blog is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
✍️ Search personal blogs and reviews for authentic user experiences. Great for product reviews, personal stories, detailed tutorials, and real user opinions. Find genuine Korean perspectives. For recent posts or. It is categorised as a Read tool in the Naver Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Naver Search MCP Server MCP server in PolicyLayer and add a rule for search_blog: 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 Naver Search MCP Server. Nothing to install.
search_blog 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_blog 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_blog. 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_blog is provided by the Naver Search MCP Server MCP server (isnow890/naver-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Naver Search MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Naver Search MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.