Low Risk

blender_system_info

blender_system_info

How to control blender_system_info ↓

What blender_system_info does on Blender

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

Low Risk

Why blender_system_info needs a policy

The name implies a read/query operation to retrieve system information about Blender or the host environment. No description is available to confirm or contradict this. Lowering confidence due to empty description. System info tools are typically read-only with low blast radius.

From the tool's definition Tool name 'blender_system_info' suggests retrieval of system information; description is empty and uninformative.

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

How to control blender_system_info

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_system_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "blender_system_info": {}
  }
}

blender_system_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about blender_system_info

What does the blender_system_info tool do? +

blender_system_info. 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_system_info? +

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

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

Can I rate-limit blender_system_info? +

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

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

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

Free to start. No card required.

77 Blender tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.