blender.health

Check Blender bridge availability

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/blender.health.md

WHAT IT DOES

What blender.health does on CoWork OS

AI agents call blender.health to retrieve information from CoWork OS 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.health is rated Low

This tool only queries whether the Blender bridge is reachable/available. It reads system state and returns status information without modifying, executing, or deleting anything. Misuse potential is negligible.

From the tool's definition "Check Blender bridge availability" — purely a status/health check with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender.health safely

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

blender.health Allowed

blender.health 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.health": {}
  }
}

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

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

FAQ

Questions about blender.health

What does the blender.health tool do? +

Check Blender bridge availability. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

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

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

What risk level is blender.health? +

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

Can I rate-limit blender.health? +

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

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

blender.health is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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