Stop the current native macro recording and save
AI agents use stop_native_macro_recording to create or update resources in Solidworks — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Solidworks environment.
This tool stops an active macro recording session and saves the result. It creates/writes a saved macro file to disk. This is reversible (the file can be deleted), so it falls under Write rather than Destructive or Execute. Misuse could save an unintended macro, but blast radius is limited.
From the tool's definition Stop the current native macro recording and save
Attacks that exploit this kind of access
Stop the current native macro recording and save. It is categorised as a Write tool in the Solidworks MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Solidworks 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. Nothing to install.
stop_native_macro_recording is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
stop_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →