Blender addon management (compatibility alias — prefer blender_addons).
AI agents use manage_blender_addons 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.
Addon management in Blender is a Write operation because it creates or modifies the application state (addon enable/disable, installation) in a reversible manner. While addons can theoretically execute code, the tool itself is primarily managing addon state rather than directly executing arbitrary operations. The scope is limited to addon lifecycle management, not arbitrary code execution.
From the tool's definition Tool name contains 'manage' and description explicitly states 'addon management', which involves installing, enabling, disabling, or modifying Blender addons. This is reversible state modification.
Documented attack patterns abuse exactly the kind of access manage_blender_addons 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_blender_addons:
{
"version": "1",
"default": "deny",
"tools": {
"manage_blender_addons": {
"limits": [
{
"counter": "manage_blender_addons_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_blender_addons 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.
Blender addon management (compatibility alias — prefer blender_addons). 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_blender_addons: 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_blender_addons 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_blender_addons 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_blender_addons. 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_blender_addons 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.