# get_object_info

Get detailed information about a specific object in the scene

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

## Facts

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

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

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

## Why get_object_info is rated Low

This tool queries and retrieves information about existing 3D objects in a Blender scene. It performs no modifications, deletions, code execution, or financial operations. The operation is read-only with no capability to alter the scene state, making it the lowest risk category.

From the tool's own definition: "Tool name 'get_object_info' and description 'Get detailed information about a specific object in the scene' indicate retrieval of data without modification or side effects."

## Use case

AI agents call get_object_info to retrieve information from BlenderMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_object_info": {}
  }
}
```

## 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
- `scale_object` — Execute — https://policylayer.com/tools/aryeon0228-blendermcp/scale-object.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