Generate VBA for setting up simulation studies
AI agents invoke vba_simulation_setup 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.
VBA generation and setup implies execution of macro/scripting code within SolidWorks. VBA execution can trigger arbitrary operations within the application (creating studies, modifying model parameters, running simulations), making this an Execute-category tool. Misuse could alter simulation configurations or trigger unintended model changes at scale, warranting high severity.
From the tool's definition 'Generate VBA for setting up simulation studies' — generates and likely executes VBA code to configure simulation studies within SolidWorks
Attacks that exploit this kind of access
Generate VBA for setting up simulation studies. 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_simulation_setup: 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_simulation_setup 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_simulation_setup 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_simulation_setup. 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_simulation_setup 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 →