Capture a screenshot of the current model view
AI agents call capture_screenshot to retrieve information from SolidWorks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool merely captures and returns visual information about the current state of SolidWorks. It performs no modifications, does not execute commands that affect the model, and has no destructive, financial, or execution side effects. This is purely a data retrieval operation, fitting the Read category with low severity since unauthorized screenshot capture poses minimal direct risk to the model itself.
From the tool's definition capture_screenshot: Capture a screenshot of the current model view - this is a read-only operation that retrieves the visual state of the CAD model without modifying, executing operations, or causing side effects.
Documented attack patterns abuse exactly the kind of access capture_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SolidWorks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"capture_screenshot": {}
}
} capture_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 a screenshot of the current model view. It is categorised as a Read tool in the SolidWorks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SolidWorks MCP Server MCP server in PolicyLayer and add a rule for capture_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 SolidWorks MCP Server. Nothing to install.
capture_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_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_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_screenshot is provided by the SolidWorks MCP Server MCP server (jianzhichun/solidworks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SolidWorks MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
84 SolidWorks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.