This record as markdown: /tools/kiln/download-and-upload.md
What download_and_upload does on Kiln
AI agents use download_and_upload to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why download_and_upload is rated Medium
The name implies a two-phase operation: downloading content (Read) and then uploading it (Write) to a destination. In the context of 3D printer control, this likely involves transferring print files to a printer, which is a Write operation. However, the description is empty, so confidence is reduced.
From the tool's definition Tool name 'download_and_upload' suggests fetching data from one location and writing it to another (e.g., downloading a file and uploading it to a printer or service).
Attacks that exploit this kind of access
The rule that runs download_and_upload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For download_and_upload, this is the rule to start with:
download_and_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every download_and_upload call is checked against it from then on.
Questions about download_and_upload
download_and_upload is a write tool on the Kiln MCP server. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for download_and_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 Kiln. Nothing to install.
download_and_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 download_and_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 download_and_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.
download_and_upload is provided by the Kiln MCP server (codeofaxel/Kiln). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue