Pause or resume the current macro recording
AI agents invoke pause_resume_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.
This tool controls macro recording state in SolidWorks, which is an active operation that affects the execution context of the application. It doesn't merely read data, but triggers state changes in an ongoing recording process. Misuse could disrupt workflow automation or cause incomplete macro recordings, making it an Execute-level action with medium severity.
From the tool's definition Pause or resume the current macro recording
Documented attack patterns abuse exactly the kind of access pause_resume_macro_recording gives an agent:
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 pause_resume_macro_recording:
{
"version": "1",
"default": "deny",
"tools": {
"pause_resume_macro_recording": {
"limits": [
{
"counter": "pause_resume_macro_recording_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} pause_resume_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.
Free to start. No card required.
Pause or resume 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.
Register the SolidWorks MCP Server MCP server in PolicyLayer and add a rule for pause_resume_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.
pause_resume_macro_recording is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pause_resume_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.
Set action: deny in the PolicyLayer policy for pause_resume_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.
pause_resume_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.
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.