blender_export_presets
A write tool on the Blender MCP server.
This record as markdown: /tools/sandraschi-blender-mcp/blender-export-presets.md
What blender_export_presets does on Blender
AI agents use blender_export_presets to create or update resources in Blender, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender environment.
Why blender_export_presets is rated Medium
The tool creates or modifies preset data (export configurations) which is reversible—presets can be deleted or overwritten. This fits the Write category (creates/modifies data reversibly). However, confidence is moderate because the description is empty. Export presets themselves are not destructive operations, but misuse in an agentic context could inadvertently overwrite important presets.
From the tool's definition Tool name 'blender_export_presets' suggests saving or modifying export configuration settings. Within Blender's context, export presets are user-defined configurations that are created and stored for reuse.
Attacks that exploit this kind of access
The rule that runs blender_export_presets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender_export_presets, this is the rule to start with:
blender_export_presets 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 Blender, apply this rule, and every blender_export_presets call is checked against it from then on.
Questions about blender_export_presets
blender_export_presets is a write tool on the Blender MCP server. It is categorised as a Write tool in the Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for blender_export_presets: 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 Blender. Nothing to install.
blender_export_presets 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_export_presets 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_export_presets. 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_export_presets is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender, and thousands of servers like it.
This server
Across the catalogue