NAVER WORKS 연결 상태를 진단합니다. 인증 정보, 토큰, Private Key, API 연결을 점검합니다.
AI agents call nworks_doctor to retrieve information from Nworks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic/health-check tool that reads and verifies connection status, authentication credentials, tokens, and API connectivity. It retrieves and inspects existing configuration without modifying or creating anything. Severity is low as it only reads diagnostic information, though it does access sensitive credential data like Private Keys.
From the tool's definition 연결 상태를 진단합니다. 인증 정보, 토큰, Private Key, API 연결을 점검합니다 (diagnoses connection status, checks authentication info, tokens, Private Key, API connections)
Documented attack patterns abuse exactly the kind of access nworks_doctor gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nworks, and nothing reaches the server without passing your rules. This is the rule we recommend for nworks_doctor:
{
"version": "1",
"default": "deny",
"tools": {
"nworks_doctor": {}
}
}nworks_doctor 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.
NAVER WORKS 연결 상태를 진단합니다. 인증 정보, 토큰, Private Key, API 연결을 점검합니다. It is categorised as a Read tool in the Nworks MCP Server, which means it retrieves data without modifying state.
Register the Nworks MCP server in PolicyLayer and add a rule for nworks_doctor: 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 Nworks. Nothing to install.
nworks_doctor 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 nworks_doctor 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 nworks_doctor. 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.
nworks_doctor is provided by the Nworks MCP server (yjcho9317/nworks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nworks, 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.
26 Nworks tools catalogued and risk-classified — across an index of 43,000+ MCP servers.