Low Risk

capture_blender_3dviewport_screenshot

capture_blender_3dviewport_screenshot

How to control capture_blender_3dviewport_screenshot ↓

AI agents call capture_blender_3dviewport_screenshot to retrieve information from IFC Bonsai MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool captures a screenshot of the 3D viewport—a read-only operation that retrieves visual information without side effects. It does not create, modify, delete, or execute code. The only minor confidence reduction from 1.0 is due to the empty description, but the function name is unambiguous. Severity is low because viewport screenshots pose minimal security risk even if misused by an agent.

From the tool's definition Tool name 'capture_blender_3dviewport_screenshot' indicates screen capture functionality. No description provided, but the name and context (IFC Bonsai MCP for viewing/editing models) clearly indicate this retrieves/captures visual data from the Blender…

Documented attack patterns abuse exactly the kind of access capture_blender_3dviewport_screenshot gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and IFC Bonsai MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_blender_3dviewport_screenshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "capture_blender_3dviewport_screenshot": {}
  }
}

capture_blender_3dviewport_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register IFC Bonsai MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the capture_blender_3dviewport_screenshot tool do? +

capture_blender_3dviewport_screenshot. It is categorised as a Read tool in the IFC Bonsai MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_blender_3dviewport_screenshot? +

Register the IFC Bonsai MCP server in PolicyLayer and add a rule for capture_blender_3dviewport_screenshot: 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 IFC Bonsai MCP. Nothing to install.

What risk level is capture_blender_3dviewport_screenshot? +

capture_blender_3dviewport_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit capture_blender_3dviewport_screenshot? +

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

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

capture_blender_3dviewport_screenshot is provided by the IFC Bonsai MCP server (show2instruct/ifc-bonsai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every IFC Bonsai MCP tool call.

Deterministic rules across all 52 IFC Bonsai MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

52 IFC Bonsai MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.