Generate VBA for creating drawing views
AI agents invoke vba_create_drawing_views to trigger actions in Solidworks. 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.
The tool generates VBA (Visual Basic for Applications) code for creating drawing views in SolidWorks. Generating and running VBA macros constitutes code execution, as VBA scripts can have broad effects depending on their content. While the primary intent is drawing view creation (a Write-level operation), the VBA generation/execution mechanism elevates this to Execute category.
From the tool's definition 'Generate VBA for creating drawing views' — generates and likely executes VBA code
Attacks that exploit this kind of access
Generate VBA for creating drawing views. It is categorised as a Execute tool in the Solidworks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Solidworks MCP server in PolicyLayer and add a rule for vba_create_drawing_views: 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. Nothing to install.
vba_create_drawing_views is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the vba_create_drawing_views 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 vba_create_drawing_views. 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.
vba_create_drawing_views is provided by the Solidworks MCP server (solidworks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →