reduce_vertex_valence
AI agents invoke reduce_vertex_valence to trigger actions in BlenderMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name suggests it modifies vertex topology in a 3D mesh (reducing the number of edges connected to a vertex), which would be a write/execute operation within Blender. However, the description is empty, so confidence is low. Given the server's context of executing Python scripts and manipulating Blender objects, this is most likely an Execute-level operation that runs geometry processing operations.
From the tool's definition Tool name 'reduce_vertex_valence' and empty description. Server context involves Blender manipulation and Python script execution.
Attacks that exploit this kind of access
reduce_vertex_valence. It is categorised as a Execute tool in the BlenderMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender MCP server in PolicyLayer and add a rule for reduce_vertex_valence: 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 BlenderMCP. Nothing to install.
reduce_vertex_valence is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reduce_vertex_valence 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 reduce_vertex_valence. 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.
reduce_vertex_valence is provided by the Blender MCP server (shirshovdim/retopoflow_blender_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →