macro_export_vba

THE RISK

High Risk

Why macro_export_vba needs a policy

Exporting a macro to VBA code produces executable script artifacts that can subsequently be run to perform arbitrary operations within SolidWorks. While the export step itself may be more of a Write action (producing a file), the primary risk is that it enables code execution workflows and the output is executable code.

From the tool's definition 'Export a recorded macro to VBA code' — exports executable VBA macro code from SolidWorks

Documented attack patterns abuse exactly the kind of access macro_export_vba gives an agent:

POLICY

How to control macro_export_vba

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 macro_export_vba:

policy.json

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

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

Create a free account and register SolidWorks MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SolidWorks MCP Server tools

Destructive extrude_cut Create a cut extrusion to remove material from an existing solid body. The sketch must be Execute batch_run_macros Run multiple macros in sequence Execute macro_start_recording Start recording a new macro Execute macro_stop_recording Stop the current macro recording Execute run_macro Run a SolidWorks macro file Execute run_vba_macro Execute a VBA macro in SolidWorks Execute sketch_arc Draw an arc in the active sketch. AUTOMATIC: This tool automatically ensures an active sk Execute start_native_macro_recording Start recording a macro using SolidWorks native VBA recorder

All 84 SolidWorks MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in SolidWorks MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about macro_export_vba

What does the macro_export_vba tool do? +

Export a recorded macro to VBA code. 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.

How do I enforce a policy on macro_export_vba? +

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

What risk level is macro_export_vba? +

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

Can I rate-limit macro_export_vba? +

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

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

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

Enforce policy on every SolidWorks MCP Server tool call.

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.

CHECK YOUR STACK →