High Risk →

macro_stop_recording

Stop the current macro recording

How to control macro_stop_recording ↓

What macro_stop_recording does on SolidWorks MCP Server

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

This tool executes an action that stops a macro recording session in SolidWorks. While not directly destructive or financial, it represents an Execute-category tool because it triggers an external operation whose effects depend on system state and could interrupt or affect ongoing macro capture.

From the tool's definition Tool name 'macro_stop_recording' and description 'Stop the current macro recording' indicate control of macro recording state in SolidWorks, which is an operation that triggers/modifies the state of an external system (the CAD application's recording…

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

How to control macro_stop_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 macro_stop_recording:

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

macro_stop_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 macro_stop_recording

What does the macro_stop_recording tool do? +

Stop the current macro recording. 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_stop_recording? +

Register the SolidWorks MCP Server MCP server in PolicyLayer and add a rule for macro_stop_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 macro_stop_recording? +

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

Can I rate-limit macro_stop_recording? +

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

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

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