dissolve_edge_loop_by_selection · Blender MCP: Risk & Policy

WHAT IT DOES

What dissolve_edge_loop_by_selection does on BlenderMCP

AI agents use dissolve_edge_loop_by_selection to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.

WHY IT NEEDS A POLICY

Why dissolve_edge_loop_by_selection needs a policy

This tool modifies 3D mesh data by removing an edge loop and merging its vertices, which is characteristic of Write operations (create or modifies data reversibly). It does not irreversibly delete the entire object or permanently corrupt data beyond recovery (Blender maintains full undo history), and it does not execute arbitrary code or external operations.

From the tool's definition Tool name 'dissolve_edge_loop_by_selection' indicates it modifies mesh geometry by dissolving (removing/merging) an edge loop.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dissolve_edge_loop_by_selection Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dissolve_edge_loop_by_selection": {
      "limits": [
        {
          "counter": "dissolve_edge_loop_by_selection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 dissolve_edge_loop_by_selection

What does the dissolve_edge_loop_by_selection tool do? +

Dissolve currently selected edge loop. It is categorised as a Write tool in the BlenderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dissolve_edge_loop_by_selection? +

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

dissolve_edge_loop_by_selection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dissolve_edge_loop_by_selection? +

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

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

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