blender_performance_monitor

THE RISK

Low Risk

Why blender_performance_monitor needs a policy

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.

Documented attack patterns abuse exactly the kind of access blender_performance_monitor gives an agent:

POLICY

How to control blender_performance_monitor

PolicyLayer is an MCP gateway — it sits between your AI agents and Blender, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_performance_monitor:

policy.json

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

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

Create a free account and register Blender — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Blender tools

Destructive clear_scene Remove all objects from the current scene. Execute blender_transform blender_transform Execute script_execute Execute Python script in Blender (headless). Execute agentic_blender_workflow agentic_blender_workflow Execute blender_animation blender_animation Execute blender_geonodes blender_geonodes Execute blender_jobs Async job queue for long-running Blender Python scripts (renders, bakes, sims). Execute blender_particles blender_particles

All 77 Blender tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about blender_performance_monitor

What does the blender_performance_monitor tool do? +

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

Enforce policy on every Blender tool call.

Start from Blender, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →