파일을 드라이브에 업로드합니다 (User OAuth file scope 필요). content(base64)와 fileName으로 전달하거나, filePath로 로컬 파일 경로를 지정합니다. MCP 클라이언트에서는 content+fileName 방식을 권장합니다.
AI agents use nworks_drive_upload 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 data (files in NAVER WORKS Drive) in a reversible manner. Users can delete or overwrite uploaded files afterward. It is not destructive (files can be recovered), not financial, and not execute (no arbitrary code execution, only file upload).
From the tool's definition Tool name contains 'upload' and description states '파일을 드라이브에 업로드합니다' (uploads files to drive). Accepts file content via base64-encoded 'content' parameter with 'fileName', or local 'filePath'. These are write operations that create new files in cloud storage.
Documented attack patterns abuse exactly the kind of access nworks_drive_upload 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_drive_upload:
{
"version": "1",
"default": "deny",
"tools": {
"nworks_drive_upload": {
"limits": [
{
"counter": "nworks_drive_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}nworks_drive_upload 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.
파일을 드라이브에 업로드합니다 (User OAuth file scope 필요). content(base64)와 fileName으로 전달하거나, filePath로 로컬 파일 경로를 지정합니다. MCP 클라이언트에서는 content+fileName 방식을 권장합니다. 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_drive_upload: 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_drive_upload 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_drive_upload 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_drive_upload. 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_drive_upload 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.