New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

blender_status

A read tool on the Blender MCP server.

SERVERBlender SOURCEsandraschi/blender-mcp
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/sandraschi-blender-mcp/blender-status.md

What blender_status does on Blender

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

Why blender_status is rated Low

Given the empty description, classification relies on the tool name. 'Status' operations conventionally retrieve information about the current state of a system without side effects. The broader server context shows destructive/write tools explicitly named (add_to_collection, blender_animation, etc.), while this tool lacks descriptive language indicating mutation.

From the tool's definition Tool name 'blender_status' with no description suggests a status-check operation that queries Blender's current state without modification. The pattern of checking application status is typical of read-only operations.

Questions about blender_status

What does the blender_status tool do? +

blender_status is a read tool on the Blender MCP server. It is categorised as a Read tool in the Blender MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on blender_status? +

Register the Blender 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. 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 MCP server (sandraschi/blender-mcp). 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Blender's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.