This record as markdown: /tools/sandraschi-blender-mcp/blender-mesh.md
What blender_mesh does on Blender
AI agents use blender_mesh to create or update resources in Blender, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender environment.
Why blender_mesh is rated Medium
The description is empty, so classification relies on context. 'blender_mesh' most likely creates or modifies mesh objects in Blender (a 3D modeling operation), which is a Write operation. It could also be Execute if it runs arbitrary mesh operations.
From the tool's definition Tool name 'blender_mesh' on a server for controlling Blender to create, manipulate, and automate 3D scenes and objects.
Attacks that exploit this kind of access
The rule that runs blender_mesh 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_mesh, this is the rule to start with:
blender_mesh stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_mesh call is checked against it from then on.
Questions about blender_mesh
blender_mesh is a write tool on the Blender MCP server. It is categorised as a Write tool in the Blender MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for blender_mesh: 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_mesh is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the blender_mesh 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_mesh. 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_mesh 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