Check for interference between components in an assembly. According to SolidWorks API documentation: - Use AssemblyDoc.InterferenceDetectionManager to access interference detection - InterferenceDetectionManager.GetInterferences() processes and finds interferences - GetInterferenceCount() returns...
AI agents call check_interference 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.
This tool only queries and retrieves interference detection results from an assembly document. It performs no modifications, deletions, or external operations. The API methods used are all getter/query methods that return data about existing interferences. Even though it operates on a CAD model, it is purely informational with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool description states 'Check for interference between components in an assembly' and API documentation specifies read-only methods: 'GetInterferences()', 'GetInterferenceCount()', and 'GetInterference()' which retrieve interference data without modifying…
Documented attack patterns abuse exactly the kind of access check_interference 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 check_interference:
{
"version": "1",
"default": "deny",
"tools": {
"check_interference": {}
}
}check_interference 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.
Check for interference between components in an assembly. According to SolidWorks API documentation: - Use AssemblyDoc.InterferenceDetectionManager to access interference detection - InterferenceDetectionManager.GetInterferences() processes and finds interferences - GetInterferenceCount() returns the number of interferences found - Individual interference details can be accessed via GetInterference() method REQUIREMENTS: - Current document must be an Assembly (type=2) - Assembly must have at least 2 components - Use get_sketch_context or check document type before calling PARAMETERS: - treatCoincidenceAsInterference: If true, coincident faces are treated as interferences - treatSubAssembliesAsComponents: If true, sub-assemblies are treated as single components - includeMultibodyParts: If true, checks interference between bodies within multibody parts. 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 check_interference: 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.
check_interference 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 check_interference 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 check_interference. 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.
check_interference 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.