Search Naver Local for restaurants, shops, and points of interest. Returns business name, address, phone, category, and map coordinates.
AI agents call search_local to retrieve information from Naver Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | 'random' (default) or 'comment' (sort by review count). |
query | string | — | Search query. Must be UTF-8 encoded. |
start | integer | — | Result offset. Local search supports only start=1. |
display | integer | — | Max 5 results per call for the local endpoint. |
Parameters from the server's own tool schema.
This is a straightforward query/search tool that retrieves publicly available local business information from Naver's local search service. It has no side effects, does not execute code, does not modify or delete data, and does not involve financial transactions. The returned data (business details and coordinates) are read-only informational results.
From the tool's definition Tool performs 'Search' operation that 'Returns business name, address, phone, category, and map coordinates' — purely retrieves public information with no modification, deletion, or execution capabilities.
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access search_local gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Naver Search, and nothing reaches the server without passing your rules. This is the rule we recommend for search_local:
{
"version": "1",
"default": "deny",
"tools": {
"search_local": {}
}
}search_local 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 Naver Local for restaurants, shops, and points of interest. Returns business name, address, phone, category, and map coordinates. It is categorised as a Read tool in the Naver Search MCP Server, which means it retrieves data without modifying state.
search_local accepts 4 parameters: sort, query, start, display. The full parameter table on this page comes from the server's own tool schema.
Register the Naver Search 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. 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 (@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, 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.
12 Naver Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.