quadriflow_remesh
AI agents invoke quadriflow_remesh 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.
QuadriFlow remeshing is a computational operation that restructures mesh topology in Blender. It triggers an external operation (mesh processing algorithm) within the Blender environment, modifying the geometry of 3D objects. While it modifies data, it is more akin to executing a processing operation than a simple write. The description is empty, lowering confidence.
From the tool's definition Tool name 'quadriflow_remesh' and server description mentions 'professional retopology workflows' and ability to 'execute Python scripts directly within the Blender environment'
Attacks that exploit this kind of access
quadriflow_remesh. 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 quadriflow_remesh: 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.
quadriflow_remesh 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 quadriflow_remesh 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 quadriflow_remesh. 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.
quadriflow_remesh 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 →