import_generated_asset
AI agents use import_generated_asset 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.
Importing an asset into a Blender scene creates or adds new data to the project reversibly (the import can be undone). This is a Write operation rather than Read (it modifies the scene), Execute (it doesn't run arbitrary code—it performs a specific import action), or Destructive (the operation is reversible).
From the tool's definition Tool name 'import_generated_asset' indicates it imports (adds/loads) generated assets into a Blender scene.
Documented attack patterns abuse exactly the kind of access import_generated_asset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for import_generated_asset:
{
"version": "1",
"default": "deny",
"tools": {
"import_generated_asset": {
"limits": [
{
"counter": "import_generated_asset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_generated_asset 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.
Free to start. No card required.
import_generated_asset. 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 import_generated_asset: 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.
import_generated_asset 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 import_generated_asset 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 import_generated_asset. 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.
import_generated_asset is provided by the Blender MCP server (vertiiii/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blender, 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.
17 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.