Returns Naver's spelling correction for a misspelled search query (오타변환).
AI agents call spellcheck_query 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 |
|---|---|---|---|
query | string | — | Search query. Must be UTF-8 encoded. |
Parameters from the server's own tool schema.
This is a read-only utility that retrieves and returns spelling correction suggestions. It queries existing Naver data and returns results without creating, modifying, deleting, or executing anything. The only potential risk is if an attacker could inject malicious input to break downstream search functionality, but the tool itself performs only data retrieval. Low severity due to minimal blast radius.
From the tool's definition Tool returns spelling corrections for search queries with no ability to modify data or trigger external operations. Description states 'Returns Naver's spelling correction' which is purely retrieval of preprocessed data.
Risk signalsAccepts freeform code/query input (query)
Documented attack patterns abuse exactly the kind of access spellcheck_query 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 spellcheck_query:
{
"version": "1",
"default": "deny",
"tools": {
"spellcheck_query": {}
}
}spellcheck_query 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.
Returns Naver's spelling correction for a misspelled search query (오타변환). It is categorised as a Read tool in the Naver Search MCP Server, which means it retrieves data without modifying state.
spellcheck_query accepts 1 parameter: query. 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 spellcheck_query: 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.
spellcheck_query 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 spellcheck_query 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 spellcheck_query. 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.
spellcheck_query 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.