Searches for local business information using the given keyword. (display maximum 5, start maximum 1) sort=
AI agents call search_local 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 public local business information in response to a keyword search. It has no side effects, cannot modify data, and does not execute code or trigger external operations. It is a straightforward Read operation with minimal security risk.
From the tool's definition Tool name 'search_local' and description 'Searches for local business information using the given keyword' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Searches for local business information using the given keyword. (display maximum 5, start maximum 1) sort=. 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_local: 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_local 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_local 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_local. 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_local 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 →