High Risk →

run_macro

Run a SolidWorks macro file

How to control run_macro ↓

What run_macro does on SolidWorks MCP Server

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

High Risk

Why run_macro needs a policy

This tool allows execution of arbitrary SolidWorks macros without apparent argument constraints or sandboxing. Macros can perform unrestricted operations within SolidWorks and the host system (file I/O, registry access, etc.). The blast radius is critical because an AI agent could be tricked into running a malicious macro that compromises the CAD system, exfiltrates designs, or executes system-level commands.

From the tool's definition Tool name 'run_macro' with description 'Run a SolidWorks macro file' explicitly indicates execution of arbitrary code.

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

How to control run_macro

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_macro": {
      "limits": [
        {
          "counter": "run_macro_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register SolidWorks MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about run_macro

What does the run_macro tool do? +

Run a SolidWorks macro file. 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 run_macro? +

Register the SolidWorks MCP Server MCP server in PolicyLayer and add a rule for run_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 MCP Server. Nothing to install.

What risk level is run_macro? +

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

Can I rate-limit run_macro? +

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

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

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

Free to start. No card required.

84 SolidWorks MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.