blender_list_tools

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-list-tools.md

WHAT IT DOES

What blender_list_tools does on Blender

AI agents call blender_list_tools 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.

RISK

Why blender_list_tools is rated Low

The tool name contains 'list', which is a classic Read operation that retrieves information about available Blender tools without modifying, executing, or destroying anything. The empty description prevents higher confidence, but the naming pattern is clear. This would typically be used for discovery purposes only.

From the tool's definition Tool name 'blender_list_tools' indicates enumeration/listing of available tools. No description provided, but the 'list' verb strongly suggests data retrieval without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blender_list_tools 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_list_tools, this is the rule to start with:

blender_list_tools Allowed

blender_list_tools 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_list_tools": {}
  }
}

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

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

FAQ

Questions about blender_list_tools

What does the blender_list_tools tool do? +

blender_list_tools 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_list_tools? +

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

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

Can I rate-limit blender_list_tools? +

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

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

blender_list_tools 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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