import_generated_asset
AI agents use import_generated_asset to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
Based on the tool name alone, this tool likely imports a previously generated asset (e.g., from Hyper3D or Poly Haven) into the Blender scene, which is a Write operation as it creates/adds new data to the scene. However, the empty description significantly lowers confidence. It could potentially trigger external operations (Execute) but the 'import' verb most naturally maps to Write.
From the tool's definition Tool name 'import_generated_asset' and empty description. The name suggests importing/bringing in a generated asset into Blender.
Attacks that exploit this kind of access
import_generated_asset. It is categorised as a Write tool in the BlenderMCP 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 BlenderMCP. 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 (spranjal3301/final-year-project). 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 →