Converts Korean/English keyboard input errors.
AI agents call correct_errata 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.
The tool reads user input containing keyboard typos and returns corrected text. This is a pure read/transform operation with no persistence, destructive capability, code execution, or financial impact. While it operates on user data, the operation is entirely reversible and informational. Severity is low because misuse would only affect search query quality, not compromise data or systems.
From the tool's definition Tool performs keyboard input error detection and conversion ('Converts Korean/English keyboard input errors'). This is a transformation/mapping operation with no data creation, modification, deletion, or external side effects.
Attacks that exploit this kind of access
Converts Korean/English keyboard input errors. 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 correct_errata: 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.
correct_errata 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 correct_errata 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 correct_errata. 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.
correct_errata is provided by the Naver Search MCP Server MCP server (jikime/py-mcp-naver-search). 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 →