Determines if the input query is an adult search term.
AI agents call check_adult_query 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 analyzes input text to categorize it (adult vs. non-adult) and returns a classification result. It retrieves or derives information from the input without side effects, modifying data, executing commands, or making financial transactions. The operation is read-only: it examines and evaluates the query content.
From the tool's definition Tool name 'check_adult_query' and description 'Determines if the input query is an adult search term' indicate a classification/detection operation with no data modification, deletion, or external action triggering.
Attacks that exploit this kind of access
Determines if the input query is an adult search term. 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 check_adult_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 MCP Server. Nothing to install.
check_adult_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 check_adult_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 check_adult_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.
check_adult_query 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 →