create_object
AI agents use create_object 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.
The name 'create_object' strongly implies creating a new 3D object in the Blender scene, which is a reversible write operation. However, the description is empty, so confidence is reduced. Based on context from sibling tools (delete_object, animate_object, get_scene_info), this server manages Blender scene objects, and 'create_object' most likely adds a new object to the scene — a Write action.
From the tool's definition Tool name: 'create_object' on a Blender MCP server focused on 3D modeling and animation.
Attacks that exploit this kind of access
create_object. 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 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 BlenderMCP. Nothing to install.
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 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 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.
create_object is provided by the Blender MCP server (richard-devbot/blender-mcp-csm). 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 →