Drop files onto an element (file input or drag-and-drop target) for uploading
AI agents invoke drop_files to trigger actions in Webclaw. 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.
This tool triggers a browser action (file drop/upload) that causes files to be uploaded to external targets. The effect depends on which element is targeted and what files are dropped, potentially uploading sensitive local files to arbitrary web destinations. It spans Write and Execute; Execute is more appropriate given it triggers an external browser operation with variable effects based on arguments.
From the tool's definition Drop files onto an element (file input or drag-and-drop target) for uploading
Documented attack patterns abuse exactly the kind of access drop_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for drop_files:
{
"version": "1",
"default": "deny",
"tools": {
"drop_files": {
"limits": [
{
"counter": "drop_files_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}drop_files stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Drop files onto an element (file input or drag-and-drop target) for uploading. It is categorised as a Execute tool in the Webclaw MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Webclaw MCP server in PolicyLayer and add a rule for drop_files: 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 Webclaw. Nothing to install.
drop_files 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 drop_files 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 drop_files. 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.
drop_files is provided by the Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Webclaw, 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.
21 Webclaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.