🛍️ STEP 2: Analyze shopping category trends over time. Use find_category first to get category codes. BUSINESS CASES: Market size analysis, seasonal trend identification, category performance comparison. EXAMPLE: Compare
AI agents call datalab_shopping_category 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 and analyzes historical shopping trend data from Naver's datalab service. It performs queries to generate insights about shopping categories but does not modify, delete, or execute any operations. The instruction to 'Use find_category first to get category codes' confirms it is a lookup/analysis step in a workflow. No side effects or irreversible actions are possible.
From the tool's definition Tool description indicates 'Analyze shopping category trends over time' and lists use cases like 'Market size analysis, seasonal trend identification, category performance comparison' — all read-only analytical operations.
Documented attack patterns abuse exactly the kind of access datalab_shopping_category gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Naver Search MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for datalab_shopping_category:
{
"version": "1",
"default": "deny",
"tools": {
"datalab_shopping_category": {}
}
}datalab_shopping_category 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.
🛍️ STEP 2: Analyze shopping category trends over time. Use find_category first to get category codes. BUSINESS CASES: Market size analysis, seasonal trend identification, category performance comparison. EXAMPLE: Compare. 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 datalab_shopping_category: 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.
datalab_shopping_category 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 datalab_shopping_category 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 datalab_shopping_category. 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.
datalab_shopping_category is provided by the Naver Search MCP Server 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 MCP Server, 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.
21 Naver Search MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.