search_naver_places
AI agents call search_naver_places to retrieve information from Korean Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on context from sibling tools and the search_ prefix, this tool retrieves data from Naver Places (a Korean business/location listing service). Search operations are Read category—they query and return data without side effects. Severity is low because search queries have minimal blast radius even if misused; they cannot modify, delete, or move resources.
From the tool's definition Tool name is 'search_naver_places' with empty description; sibling tools on the server (get_melon_chart, get_musinsa_ranking, get_naver_place_reviews, search_naver_news, search_bunjang, search_daangn) are all data retrieval/search functions.
Attacks that exploit this kind of access
search_naver_places. It is categorised as a Read tool in the Korean Data MCP Server, which means it retrieves data without modifying state.
Register the Korean Data MCP server in PolicyLayer and add a rule for search_naver_places: 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 Korean Data. Nothing to install.
search_naver_places 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_naver_places 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_naver_places. 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_naver_places is provided by the Korean Data MCP server (leadbrain/korean-data-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 →