NAVER WORKS API 인증 정보를 설정합니다. ■ 사전 준비 (사용자가 직접 해야 함): 1. https://dev.worksmobile.com 에서 앱 생성 후 Client ID와 Client Secret을 발급받습니다. 2. MCP 설정 파일(예: claude_desktop_config.json)의 nworks 서버에 env 필드를 추가합니다: {
AI agents use nworks_setup to create or update resources in Nworks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nworks environment.
This tool creates or modifies authentication configuration data (Client ID, Client Secret in the MCP config file). While it doesn't directly delete data, it irreversibly changes security-critical authentication settings that could grant unauthorized access if misconfigured.
From the tool's definition Tool description states it "설정합니다" (sets up/configures) NAVER WORKS API authentication information, involving Client ID and Client Secret credentials. The tool writes/stores authentication configuration to the MCP settings file.
Documented attack patterns abuse exactly the kind of access nworks_setup 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_setup:
{
"version": "1",
"default": "deny",
"tools": {
"nworks_setup": {
"limits": [
{
"counter": "nworks_setup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}nworks_setup stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
NAVER WORKS API 인증 정보를 설정합니다. ■ 사전 준비 (사용자가 직접 해야 함): 1. https://dev.worksmobile.com 에서 앱 생성 후 Client ID와 Client Secret을 발급받습니다. 2. MCP 설정 파일(예: claude_desktop_config.json)의 nworks 서버에 env 필드를 추가합니다: {. It is categorised as a Write tool in the Nworks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nworks MCP server in PolicyLayer and add a rule for nworks_setup: 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_setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nworks_setup 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_setup. 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_setup 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.