blender_performance_monitor

A other tool on the Blender MCP server.

SERVERBlender SOURCEsandraschi/blender-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sandraschi-blender-mcp/blender-performance-monitor.md

WHAT IT DOES

What blender_performance_monitor does on Blender

AI agents call blender_performance_monitor as a supporting operation in Blender workflows.

RISK

Why blender_performance_monitor is rated Low

The name suggests monitoring/reading performance metrics, which would be a Read operation. However, with an empty description, there is insufficient information to confidently classify it. Monitoring tools typically only read data, so severity is low, but confidence is minimal.

From the tool's definition Tool name is 'blender_performance_monitor'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_performance_monitor safely

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

blender_performance_monitor Rate-limited

blender_performance_monitor gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender_performance_monitor": {
      "limits": [
        {
          "counter": "blender_performance_monitor_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about blender_performance_monitor

What does the blender_performance_monitor tool do? +

blender_performance_monitor is a other tool on the Blender MCP server. It is categorised as a Other tool in the Blender MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on blender_performance_monitor? +

Register the Blender MCP server in PolicyLayer and add a rule for blender_performance_monitor: 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_performance_monitor? +

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

Can I rate-limit blender_performance_monitor? +

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

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

blender_performance_monitor 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.

KEEP EXPLORING

More on Blender, and thousands of servers like it.

This server

All 81 Blender tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →