blender_categories
A other tool on the Blender MCP server.
This record as markdown: /tools/sandraschi-blender-mcp/blender-categories.md
What blender_categories does on Blender
AI agents call blender_categories as a supporting operation in Blender workflows.
Why blender_categories is rated Low
With no description provided, the tool name alone ('blender_categories') suggests it may list or organize categories within Blender, implying a Read operation. However, given the empty description, confidence is very low. Defaulting to Other due to insufficient information, though it could be Read if it merely enumerates Blender categories.
From the tool's definition Tool description is empty and the name 'blender_categories' does not clearly indicate any destructive, financial, execute, write, or read operation.
Attacks that exploit this kind of access
The rule that runs blender_categories 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_categories, this is the rule to start with:
blender_categories gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender, apply this rule, and every blender_categories call is checked against it from then on.
Questions about blender_categories
blender_categories 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.
Register the Blender MCP server in PolicyLayer and add a rule for blender_categories: 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.
blender_categories is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the blender_categories 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.
Set action: deny in the PolicyLayer policy for blender_categories. 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.
blender_categories 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.
More on Blender, and thousands of servers like it.
This server
Across the catalogue