Download file from URL and save to Blender project directory. Supports downloading assets, textures, and reference materials from external sources. Args: - url (string): URL to download from - destination_path (string): Destination file path (relative to project) - timeout (number, default 30000)...
AI agents use blender_download_file to create or update resources in ClaudeKit Blender MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClaudeKit Blender MCP environment.
This tool fetches data from an arbitrary external URL and writes it to the local filesystem. The Write category applies because it creates new files on disk. Severity is high because an AI agent could be directed to download malicious payloads, exfiltrate-triggering content, or overwrite existing project files via path traversal in destination_path.
From the tool's definition Download file from URL and save to Blender project directory. Supports downloading assets, textures, and reference materials from external sources.
Attacks that exploit this kind of access
Download file from URL and save to Blender project directory. Supports downloading assets, textures, and reference materials from external sources. Args: - url (string): URL to download from - destination_path (string): Destination file path (relative to project) - timeout (number, default 30000): Download timeout in milliseconds Returns: Download confirmation with file size, type, and save location Examples: - Download texture: url=. It is categorised as a Write tool in the ClaudeKit Blender MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClaudeKit Blender MCP server in PolicyLayer and add a rule for blender_download_file: 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 ClaudeKit Blender MCP. Nothing to install.
blender_download_file 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 blender_download_file 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 blender_download_file. 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.
blender_download_file is provided by the ClaudeKit Blender MCP server (olbboy/claudekit-blender-mcp). 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 →