AI agents call blender_atlasing as a supporting operation in Blender workflows.
The description is empty and uninformative. 'Atlasing' in 3D context typically refers to UV/texture atlas operations (packing textures), which could be a Write operation, but without any description I cannot confidently assign a category. Defaulting to Other with low confidence.
From the tool's definition Tool name is 'blender_atlasing' with an empty description. No functional details are available.
Documented attack patterns abuse exactly the kind of access blender_atlasing 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 blender_atlasing:
{
"version": "1",
"default": "deny",
"tools": {
"blender_atlasing": {
"limits": [
{
"counter": "blender_atlasing_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}blender_atlasing gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
blender_atlasing. It is categorised as a Other tool in the Blender MCP Server, which means it performs auxiliary operations.
Register the Blender MCP server in PolicyLayer and add a rule for blender_atlasing: 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.
blender_atlasing is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the blender_atlasing 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_atlasing. 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_atlasing 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.