Generate VBA for managing configurations
AI agents invoke vba_configurations to trigger actions in SolidWorks MCP Server. 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 code that is run via the COM bridge to SolidWorks to manage model configurations. Executing VBA in a CAD environment can modify model state, configurations, and geometry in ways that may be difficult to reverse, placing it in the Execute category. Severity is high because arbitrary VBA execution in SolidWorks can alter or overwrite design data across configurations.
From the tool's definition Generate VBA for managing configurations — generates and likely executes VBA code through the COM bridge to control SolidWorks
Documented attack patterns abuse exactly the kind of access vba_configurations 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 vba_configurations:
{
"version": "1",
"default": "deny",
"tools": {
"vba_configurations": {
"limits": [
{
"counter": "vba_configurations_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}vba_configurations stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate VBA for managing configurations. It is categorised as a Execute tool in the SolidWorks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SolidWorks MCP Server MCP server in PolicyLayer and add a rule for vba_configurations: 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.
vba_configurations 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_configurations 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_configurations. 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_configurations 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.