AI agents invoke macro_start_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 allows starting macro recording in SolidWorks, which captures and enables execution of scripted operations. While macro recording itself is reversible, it enables the creation of code that can perform Execute-category actions (running scripts, triggering external operations). The tool directly facilitates executable automation and falls into the Execute category.
From the tool's definition The tool 'macro_start_recording' initiates recording of a macro in SolidWorks. Macros are executable scripts that can automate arbitrary operations within the CAD application, including model modifications, file operations, and external actions.
Documented attack patterns abuse exactly the kind of access macro_start_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 macro_start_recording:
{
"version": "1",
"default": "deny",
"tools": {
"macro_start_recording": {
"limits": [
{
"counter": "macro_start_recording_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} macro_start_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.
Start recording a new macro. 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 macro_start_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.
macro_start_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 macro_start_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 macro_start_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.
macro_start_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.