Add an object to a collection.
AI agents use add_to_collection 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.
Adding an object to a collection modifies scene structure but is fully reversible (the object can be removed from the collection). It does not execute external code, delete data, or have financial consequences. This is a standard Write operation that creates or modifies data in a reversible manner.
From the tool's definition Tool performs 'Add an object to a collection' which creates a new organizational relationship in Blender's scene hierarchy. This is a reversible modification operation that does not delete, execute arbitrary code, or cause financial impact.
Documented attack patterns abuse exactly the kind of access add_to_collection 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 add_to_collection:
{
"version": "1",
"default": "deny",
"tools": {
"add_to_collection": {
"limits": [
{
"counter": "add_to_collection_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_to_collection 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.
Add an object to a collection. 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 add_to_collection: 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.
add_to_collection 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 add_to_collection 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 add_to_collection. 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.
add_to_collection 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.