This record as markdown: /tools/aryeon0228-blendermcp/scale-object.md
What scale_object does on BlenderMCP
AI agents invoke scale_object to trigger actions in BlenderMCP. 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 scale_object is rated High
While scaling is reversible (unlike deletion), it is an Execute-category action because it triggers a transformation operation in Blender whose outcome depends on supplied parameters. It is not Read (has side effects), not Write (modifies geometry rather than creating structured data), not Destructive (reversible), not Financial, and not Other.
From the tool's definition The tool 'scale_object' modifies 3D objects in Blender by changing their dimensions. As part of a suite that includes 'execute_blender_code' and 'render_scene', it performs an operation whose effects depend on arguments (object selection, scale factors).
Attacks that exploit this kind of access
The rule that runs scale_object safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BlenderMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scale_object, this is the rule to start with:
scale_object 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 BlenderMCP, apply this rule, and every scale_object call is checked against it from then on.
Questions about scale_object
Scale an object. It is categorised as a Execute tool in the BlenderMCP 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 scale_object: 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 BlenderMCP. Nothing to install.
scale_object 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 scale_object 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 scale_object. 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.
scale_object is provided by the Blender MCP server (aryeon0228/blendermcp). 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