capture_blender_window_screenshot
AI agents call capture_blender_window_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.
Capturing a screenshot is a read-only operation that retrieves visual data without modifying, executing code, deleting data, or creating financial obligations. The blast radius is minimal—an AI agent misusing this can only generate unwanted screenshots, not cause harm to the IFC model or system.
From the tool's definition Tool name 'capture_blender_window_screenshot' indicates image capture/retrieval from Blender viewport. No description provided, but sibling tool 'capture_blender_3dviewport_screenshot' on the same server suggests this is a screenshot/visualization retrieval…
Documented attack patterns abuse exactly the kind of access capture_blender_window_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_window_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"capture_blender_window_screenshot": {}
}
}capture_blender_window_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
capture_blender_window_screenshot. It is categorised as a Read tool in the IFC Bonsai MCP MCP Server, which means it retrieves data without modifying state.
Register the IFC Bonsai MCP server in PolicyLayer and add a rule for capture_blender_window_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.
capture_blender_window_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the capture_blender_window_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.
Set action: deny in the PolicyLayer policy for capture_blender_window_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.
capture_blender_window_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.
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.