Save base64 encoded file data to the Blender project directory. Supports saving various file types including assets, textures, and project files. Args: - file_path (string): Destination file path (relative to project) - data (string): Base64 encoded file data - overwrite (boolean, default false):...
AI agents use blender_save_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 creates or modifies files in the Blender project directory, which is a Write operation. It is not Read (no data retrieval), not Execute (does not run commands or arbitrary code—it only saves data), not Destructive (overwrite is optional and the operation is reversible by saving a different file), not Financial.
From the tool's definition Tool saves files to the Blender project directory and supports an 'overwrite' parameter, enabling modification of project files.
Attacks that exploit this kind of access
Save base64 encoded file data to the Blender project directory. Supports saving various file types including assets, textures, and project files. Args: - file_path (string): Destination file path (relative to project) - data (string): Base64 encoded file data - overwrite (boolean, default false): Overwrite existing file Returns: File save confirmation with size and type information Examples: - Save texture: file_path=. 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_save_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_save_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_save_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_save_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_save_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 →