start_native_macro_recording · Solidworks MCP: Risk & Policy

WHAT IT DOES

What start_native_macro_recording does on Solidworks

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

This tool enables execution of arbitrary VBA macros in SolidWorks. While it initiates recording rather than directly executing user-supplied code, the recorded macro can perform any operation the SolidWorks API permits—including file modifications, design alterations, and external integrations. An AI agent could record malicious macro sequences or replay recorded macros with unintended consequences.

From the tool's definition Tool description explicitly states 'Start recording a macro using SolidWorks native VBA recorder'. Recording macros captures and executes arbitrary VBA code within the SolidWorks application context, which runs code whose effects depend on what actions are…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_native_macro_recording Rate-limited

start_native_macro_recording 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": {
    "start_native_macro_recording": {
      "limits": [
        {
          "counter": "start_native_macro_recording_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 start_native_macro_recording

What does the start_native_macro_recording tool do? +

Start recording a macro using SolidWorks native VBA recorder. 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 start_native_macro_recording? +

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

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

Can I rate-limit start_native_macro_recording? +

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

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

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