Search Naver Shopping's product catalog. Returns product title, price, mall name, and product page link.
AI agents call search_shopping 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 | — | 'sim' (relevance), 'date' (newest), 'asc' (price asc), 'dsc' (price desc). |
query | string | — | Search query. Must be UTF-8 encoded. |
start | integer | — | Result offset (1-indexed). Default 1, max 1000. |
filter | string | — | Filter by product type: 'naverpay' for Naver Pay-eligible only. |
display | integer | — | Number of results per page. Default 10, max 100. |
exclude | string | — | Exclude product types: 'used', 'rental', or 'cbshop' (cross-border). |
Parameters from the server's own tool schema.
This tool queries a product catalog and retrieves information. It exhibits no capability to modify, delete, execute code, or commit financial transactions. The action is a straightforward read operation analogous to the sibling search tools on this server. Severity is low because misuse would only expose publicly available product information.
From the tool's definition Tool 'search_shopping' performs a search operation that 'Returns product title, price, mall name, and product page link' — pure data retrieval with no modification or side effects.
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access search_shopping 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_shopping:
{
"version": "1",
"default": "deny",
"tools": {
"search_shopping": {}
}
}search_shopping 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 Shopping's product catalog. Returns product title, price, mall name, and product page link. It is categorised as a Read tool in the Naver Search MCP Server, which means it retrieves data without modifying state.
search_shopping accepts 6 parameters: sort, query, start, filter, display, exclude. 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_shopping: 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_shopping 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_shopping 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_shopping. 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_shopping 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.