manage_blender_addons
A execute tool on the Blender MCP server.
This record as markdown: /tools/sandraschi-blender-mcp/manage-blender-addons.md
What manage_blender_addons does on Blender
AI agents invoke manage_blender_addons to trigger actions in Blender. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why manage_blender_addons is rated High
Managing addons in Blender typically involves enabling, disabling, installing, or removing addons — actions that can modify Blender's functionality and environment. This spans Write to Destructive depending on the operation. The name 'manage' suggests CRUD-level control.
From the tool's definition Tool name: 'manage_blender_addons'; server description mentions 'automate' and 'control of Blender'
Attacks that exploit this kind of access
The rule that runs manage_blender_addons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_blender_addons, this is the rule to start with:
manage_blender_addons stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender, apply this rule, and every manage_blender_addons call is checked against it from then on.
Questions about manage_blender_addons
manage_blender_addons is a execute tool on the Blender MCP server. It is categorised as a Execute tool in the Blender MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
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 Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
More on Blender, and thousands of servers like it.
Across the catalogue