High Risk →

stop_native_macro_recording

Stop the current native macro recording and save

How to control stop_native_macro_recording ↓

What stop_native_macro_recording does on SolidWorks MCP Server

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

This tool executes a command that halts a native macro recording session and saves it to persistent storage. While not immediately destructive (the macro itself is not executed), it performs a state-changing operation on the SolidWorks application. The severity is medium because misuse could result in unintended macros being saved and potentially executed later, or disruption of intentional macro recording workflows.

From the tool's definition Tool name 'stop_native_macro_recording' explicitly indicates stopping and saving a macro recording. The description confirms this is an action that triggers SolidWorks to halt and persist recorded macro operations.

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

How to control stop_native_macro_recording

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

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

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

  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 stop_native_macro_recording

What does the stop_native_macro_recording tool do? +

Stop the current native macro recording and save. 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 stop_native_macro_recording? +

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

What risk level is stop_native_macro_recording? +

stop_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 stop_native_macro_recording? +

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

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

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