run_vba_macro · Solidworks MCP: Risk & Policy

WHAT IT DOES

What run_vba_macro does on Solidworks

AI agents invoke run_vba_macro 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 run_vba_macro needs a policy

This tool triggers execution of Visual Basic for Applications code in SolidWorks, which can perform side effects that depend entirely on the macro's contents (file I/O, CAD model manipulation, external API calls, etc.). While not inherently destructive or financial, it grants code execution capability, making it Execute-category.

From the tool's definition Tool name explicitly states 'run_vba_macro' and description confirms it 'Execute[s] a VBA macro in SolidWorks'. VBA macros can execute arbitrary code within the SolidWorks environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_vba_macro Rate-limited

run_vba_macro 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": {
    "run_vba_macro": {
      "limits": [
        {
          "counter": "run_vba_macro_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 run_vba_macro

What does the run_vba_macro tool do? +

Execute a VBA macro in SolidWorks. 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 run_vba_macro? +

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

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

Can I rate-limit run_vba_macro? +

Yes. Add a rate_limit block to the run_vba_macro 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 run_vba_macro completely? +

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

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