Search public Naver Cafe (community forum) posts.
AI agents call search_cafe_articles 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' for relevance (default), 'date' for newest-first. |
query | string | — | Search query. Must be UTF-8 encoded. |
start | integer | — | Result offset (1-indexed). Default 1, max 1000. |
display | integer | — | Number of results to return per page. Default 10, max 100. |
Parameters from the server's own tool schema.
This tool retrieves and queries publicly available community forum posts without creating, modifying, deleting, or executing any operations. It is a read-only search function with minimal risk of misuse—the worst case would be retrieving publicly accessible information.
From the tool's definition Tool name 'search_cafe_articles' and description 'Search public Naver Cafe (community forum) posts' indicate data retrieval only. The verb 'search' combined with 'public' posts confirms query-only functionality with no modification or execution capability.
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access search_cafe_articles 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_cafe_articles:
{
"version": "1",
"default": "deny",
"tools": {
"search_cafe_articles": {}
}
}search_cafe_articles 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 public Naver Cafe (community forum) posts. It is categorised as a Read tool in the Naver Search MCP Server, which means it retrieves data without modifying state.
search_cafe_articles 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_cafe_articles: 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_cafe_articles 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_cafe_articles 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_cafe_articles. 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_cafe_articles 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.