Create a new 3D object in the current Blender scene.
AI agents use blender_create_object to create or update resources in Polybridge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Polybridge MCP environment.
Creating a 3D object is a reversible write operation. The object can be deleted, modified, or undone within Blender. It does not execute arbitrary code (unlike blender_execute_script), does not delete data irreversibly (unlike fs_delete_file), and does not trigger financial transactions.
From the tool's definition Tool name and description indicate 'Create a new 3D object in the current Blender scene' — this creates new data in a Blender project that can be modified or deleted later.
Attacks that exploit this kind of access
Create a new 3D object in the current Blender scene. It is categorised as a Write tool in the Polybridge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Polybridge MCP server in PolicyLayer and add a rule for blender_create_object: 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 Polybridge MCP. Nothing to install.
blender_create_object 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_create_object 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_create_object. 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_create_object is provided by the Polybridge MCP server (madjeek-web/polybridge-mcp). 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 →