Searches for blogs on Naver using the given keyword. The page parameter allows for page navigation.
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 retrieves blog search results from Naver's search API. It has no capability to modify, delete, or execute actions—it only queries and returns data. The severity is low because misuse (e.g., excessive searches) poses minimal risk compared to write, execute, or destructive operations. Confidence is high given the clear read-only semantics.
From the tool's definition Tool name 'search_blog' and description 'Searches for blogs on Naver using the given keyword' indicate a query/retrieval operation with no side effects. The 'page parameter allows for page navigation' confirms read-only functionality.
Attacks that exploit this kind of access
Searches for blogs on Naver using the given keyword. The page parameter allows for page navigation. 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 (jikime/py-mcp-naver-search). 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 →