Import generated asset by UUID (MAIN_SITE) or request_id (FAL_AI).
AI agents use import_generated_asset to create or update resources in Blender MCP Router — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender MCP Router environment.
This tool creates or modifies data in the Blender scene by importing assets into it. While it does not delete or overwrite existing assets irreversibly (thus not Destructive), and does not execute arbitrary code (thus not Execute in the dangerous sense), it does persistently alter the 3D scene.
From the tool's definition Tool description states 'Import generated asset' by UUID or request_id. 'Import' indicates the tool integrates external 3D assets into the Blender scene, creating or modifying the project state.
Attacks that exploit this kind of access
Import generated asset by UUID (MAIN_SITE) or request_id (FAL_AI). It is categorised as a Write tool in the Blender MCP Router MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP Router 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 MCP Router. 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 Router MCP server (mustafa-boorenie/blessed-mcp-server). 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 →