Run multiple macros in sequence
AI agents invoke batch_run_macros to trigger actions in Solidworks. 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 executes macros, which are arbitrary code sequences in SolidWorks. While individual macros might be benign, batch execution of multiple macros without visibility into their content represents a significant execute risk—the tool can trigger complex workflows, modify designs, access files, or interact with external systems depending on what the macros contain.
From the tool's definition Tool name 'batch_run_macros' and description 'Run multiple macros in sequence' indicate execution of arbitrary code/macros.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Run multiple macros in sequence. It is categorised as a Execute tool in the Solidworks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Solidworks MCP server in PolicyLayer and add a rule for batch_run_macros: 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.
batch_run_macros 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 batch_run_macros 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 batch_run_macros. 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.
batch_run_macros 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 →