Create a new object in the Blender scene. Parameters: - type: Object type (CUBE, SPHERE, CYLINDER, PLANE, CONE, TORUS, EMPTY, CAMERA, LIGHT) - name: Optional name for the object - location: Optional [x, y, z] location coordinates - rotation: Optional [x, y, z] rotation in radians - scale: Optiona...
AI agents use create_object to create or update resources in Tripo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tripo MCP Server environment.
This tool creates new data (3D objects) in the Blender scene, which is a reversible modification. It does not execute arbitrary code, delete data, or produce financial effects. While the sibling tool 'execute_blender_code' would be Execute category, 'create_object' is narrowly scoped to object instantiation with specified parameters.
From the tool's definition Tool creates a new object in the Blender scene with parameters for type, name, location, rotation, and scale. The description explicitly states 'Create a new object' which is a write operation that modifies the scene state.
Documented attack patterns abuse exactly the kind of access create_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tripo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_object:
{
"version": "1",
"default": "deny",
"tools": {
"create_object": {
"limits": [
{
"counter": "create_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_object stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new object in the Blender scene. Parameters: - type: Object type (CUBE, SPHERE, CYLINDER, PLANE, CONE, TORUS, EMPTY, CAMERA, LIGHT) - name: Optional name for the object - location: Optional [x, y, z] location coordinates - rotation: Optional [x, y, z] rotation in radians - scale: Optional [x, y, z] scale factors. It is categorised as a Write tool in the Tripo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tripo MCP Server 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 Tripo MCP Server. 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 Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.