AI agents invoke offline_download to trigger actions in Netdisk. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Offline download typically triggers an external operation where the cloud storage service fetches a remote URL/resource and saves it to the user's cloud drive. This is an Execute-category action (triggers external operation with side effects), with Write characteristics as well. Since it initiates an external fetch and storage operation, Execute is the most appropriate category.
From the tool's definition Tool name 'offline_download' on a server described as enabling 'offline download' operations for cloud storage (Quark and 115 drives). The description is empty, lowering confidence.
Attacks that exploit this kind of access
offline_download. It is categorised as a Execute tool in the Netdisk MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Netdisk MCP server in PolicyLayer and add a rule for offline_download: 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 Netdisk. Nothing to install.
offline_download is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the offline_download 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 offline_download. 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.
offline_download is provided by the Netdisk MCP server (ptbsare/netdisk-mcp-server). 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 →