vba_assembly_components · Solidworks MCP: Risk & Policy

WHAT IT DOES

What vba_assembly_components does on Solidworks

AI agents invoke vba_assembly_components 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.

WHY IT NEEDS A POLICY

Why vba_assembly_components needs a policy

This tool generates VBA (Visual Basic for Applications) code for inserting and managing components in SolidWorks assemblies. VBA generation implies the code will be executed within SolidWorks to perform operations. Executing VBA scripts can have wide-ranging effects depending on the generated code — modifying assembly structures, inserting parts, or triggering further automation.

From the tool's definition Generate VBA for inserting and managing components

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vba_assembly_components Rate-limited

vba_assembly_components 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vba_assembly_components": {
      "limits": [
        {
          "counter": "vba_assembly_components_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Solidworks, so you can run agents against it safely.

FAQ

Questions about vba_assembly_components

What does the vba_assembly_components tool do? +

Generate VBA for inserting and managing components. 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.

How do I enforce a policy on vba_assembly_components? +

Register the Solidworks MCP server in PolicyLayer and add a rule for vba_assembly_components: 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.

What risk level is vba_assembly_components? +

vba_assembly_components is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vba_assembly_components? +

Yes. Add a rate_limit block to the vba_assembly_components 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.

How do I block vba_assembly_components completely? +

Set action: deny in the PolicyLayer policy for vba_assembly_components. 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.

What MCP server provides vba_assembly_components? +

vba_assembly_components 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.