select_edge_loop · Blender MCP: Risk & Policy

WHAT IT DOES

What select_edge_loop does on BlenderMCP

AI agents invoke select_edge_loop 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.

WHY IT NEEDS A POLICY

Why select_edge_loop needs a policy

This tool modifies Blender's internal selection state by executing a selection operation. It doesn't read/query data in a neutral sense, nor does it create/delete geometry, but it triggers an action within the Blender environment that changes application state. Selection changes can cascade into subsequent operations, making it an Execute-category tool.

From the tool's definition 'Select the edge loop containing the specified edge' — triggers a selection operation within the Blender environment, altering the active selection state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_edge_loop Rate-limited

select_edge_loop stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "select_edge_loop": {
      "limits": [
        {
          "counter": "select_edge_loop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches BlenderMCP, so you can run agents against it safely.

FAQ

Questions about select_edge_loop

What does the select_edge_loop tool do? +

Select the edge loop containing the specified edge. 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.

How do I enforce a policy on select_edge_loop? +

Register the Blender MCP server in PolicyLayer and add a rule for select_edge_loop: 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.

What risk level is select_edge_loop? +

select_edge_loop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit select_edge_loop? +

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

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

select_edge_loop 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.