toggle_wireframe_overlay · Blender MCP: Risk & Policy

WHAT IT DOES

What toggle_wireframe_overlay does on BlenderMCP

AI agents invoke toggle_wireframe_overlay 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 toggle_wireframe_overlay needs a policy

This tool triggers an action within the Blender environment (toggling/setting the wireframe overlay display state). It's not purely reading data—it changes the application's view state. It's not creating/modifying scene data (Write), and it's not destructive or financial. 'Execute' best fits as it triggers an external operation (modifying Blender's UI/viewport state).

From the tool's definition Toggle or set wireframe overlay visibility

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggle_wireframe_overlay Rate-limited

toggle_wireframe_overlay 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": {
    "toggle_wireframe_overlay": {
      "limits": [
        {
          "counter": "toggle_wireframe_overlay_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 toggle_wireframe_overlay

What does the toggle_wireframe_overlay tool do? +

Toggle or set wireframe overlay visibility. 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 toggle_wireframe_overlay? +

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

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

Can I rate-limit toggle_wireframe_overlay? +

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

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

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