manage_object_construction
AI agents use manage_object_construction to create or update resources in Blender — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender environment.
The name suggests creating or modifying 3D objects in Blender (construction implies building/modifying). In the context of a Blender MCP server, this likely creates or updates scene objects, which maps to Write. However, with no description, confidence is low and severity is medium since misuse could corrupt or alter a 3D scene but is generally reversible.
From the tool's definition Tool name 'manage_object_construction' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access manage_object_construction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_object_construction:
{
"version": "1",
"default": "deny",
"tools": {
"manage_object_construction": {
"limits": [
{
"counter": "manage_object_construction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_object_construction 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.
manage_object_construction. It is categorised as a Write tool in the Blender 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 manage_object_construction: 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. Nothing to install.
manage_object_construction 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 manage_object_construction 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 manage_object_construction. 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.
manage_object_construction is provided by the Blender MCP server (sandraschi/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.