blender_status

Check Blender connection status, executable path, and scene summary.

SERVERBlender Copilot MCP Server SOURCEdwgx/blender-copilot

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/dwgx-blender-copilot/blender-status.md

WHAT IT DOES

What blender_status does on Blender Copilot MCP Server

AI agents call blender_status to retrieve information from Blender Copilot MCP Server 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_status is rated Low

This tool retrieves information about the Blender application state and scene—connection status, executable path, and scene summary. These are pure queries with no side effects, reversible operations, code execution, data destruction, or financial impact. It falls squarely into the Read category with low severity since even unrestricted access poses minimal risk.

From the tool's definition Tool name 'blender_status' and description 'Check Blender connection status, executable path, and scene summary' indicate read-only operations that query state without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_status safely

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

blender_status Allowed

blender_status 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_status": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every blender_status call is checked against it from then on.

FAQ

Questions about blender_status

What does the blender_status tool do? +

Check Blender connection status, executable path, and scene summary. It is categorised as a Read tool in the Blender Copilot MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on blender_status? +

Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for blender_status: 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 Copilot MCP Server. Nothing to install.

What risk level is blender_status? +

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

Can I rate-limit blender_status? +

Yes. Add a rate_limit block to the blender_status 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_status completely? +

Set action: deny in the PolicyLayer policy for blender_status. 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_status? +

blender_status is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Blender Copilot MCP Server, and thousands of servers like it.

This server

All 307 Blender Copilot MCP Server tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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