Import a generated 3D asset from Rodin
AI agents use import_generated_asset to create or update resources in MCP-Blender — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Blender environment.
Importing an asset modifies the Blender project by adding new geometry/content to the scene. This is a reversible write operation—the imported asset can be deleted or the project discarded. It does not execute arbitrary code, delete data irreversibly, or trigger financial transactions.
From the tool's definition Tool description states 'Import a generated 3D asset from Rodin', which creates or adds new content to the Blender project. The sibling tool 'execute_code' and the server's focus on direct Blender control indicate these tools modify the 3D scene state.
Attacks that exploit this kind of access
Import a generated 3D asset from Rodin. It is categorised as a Write tool in the MCP-Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-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 MCP-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 MCP-Blender MCP server (shdann/mcp-blend). 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 →