# scale_object

Scale an object

Agent View of the PolicyLayer registry record for `scale_object`. HTML page: https://policylayer.com/tools/aryeon0228-blendermcp/scale-object

## Facts

- Tool: `scale_object`
- Server: BlenderMCP (`aryeon0228/blendermcp`) — https://policylayer.com/tools/aryeon0228-blendermcp.md
- Homepage: https://github.com/Aryeon0228/BlenderMCP
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "scale_object",
    "arguments": {}
  }
}
```

## 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 own 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)."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches BlenderMCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scale_object": {
      "limits": [
        {
          "counter": "scale_object_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on BlenderMCP (11)

- `delete_object` — Destructive — https://policylayer.com/tools/aryeon0228-blendermcp/delete-object.md
- `execute_blender_code` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/execute-blender-code.md
- `render_scene` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/render-scene.md
- `get_object_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-object-info.md
- `get_scene_info` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-scene-info.md
- `get_viewport_screenshot` — Read — https://policylayer.com/tools/aryeon0228-blendermcp/get-viewport-screenshot.md
- `create_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/create-object.md
- `move_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/move-object.md
- `rotate_object` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/rotate-object.md
- `save_blend_file` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/save-blend-file.md
- `set_material` — Write — https://policylayer.com/tools/aryeon0228-blendermcp/set-material.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aryeon0228-blendermcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aryeon0228-blendermcp