blender.inspect

Queue safe headless inventory of the latest imported Blender scene.

SERVERVisionmcp SOURCEjoshuahickscorp/visionmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/visionmcp/blender.inspect.md

WHAT IT DOES

What blender.inspect does on Visionmcp

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

RISK

Why blender.inspect is rated Low

This tool performs a read-only inspection of Blender scene data. The description indicates it creates an inventory (lists/queries scene contents) without any side effects, modifications, or code execution. The use of 'safe' and 'inventory' further supports that this is a non-destructive data retrieval operation.

From the tool's definition "Queue safe headless inventory of the latest imported Blender scene" — the tool inspects and inventories an existing scene without modification or execution of operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender.inspect safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For blender.inspect, this is the rule to start with:

blender.inspect Allowed

blender.inspect is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender.inspect": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every blender.inspect call is checked against it from then on.

FAQ

Questions about blender.inspect

What does the blender.inspect tool do? +

Queue safe headless inventory of the latest imported Blender scene. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on blender.inspect? +

Register the Vision MCP server in PolicyLayer and add a rule for blender.inspect: 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 Visionmcp. Nothing to install.

What risk level is blender.inspect? +

blender.inspect is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit blender.inspect? +

Yes. Add a rate_limit block to the blender.inspect 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.

How do I block blender.inspect completely? +

Set action: deny in the PolicyLayer policy for blender.inspect. 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.

What MCP server provides blender.inspect? +

blender.inspect is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vision, and thousands of servers like it.

This server

All 376 Vision tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →