AI agents invoke batch_run_macros 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.
Running macros in SolidWorks constitutes code execution with effects dependent on the macro arguments/content. While not inherently destructive or financial, macro execution can modify designs, trigger external operations, or cause side effects that are difficult to predict or reverse. The batch nature amplifies the risk by executing multiple macros in sequence, increasing potential for cascading unintended effects.
From the tool's definition Tool name 'batch_run_macros' and description 'Run multiple macros in sequence' indicate execution of arbitrary code through SolidWorks macros, which can perform unpredictable operations depending on macro content.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_run_macros 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 batch_run_macros:
{
"version": "1",
"default": "deny",
"tools": {
"batch_run_macros": {
"limits": [
{
"counter": "batch_run_macros_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}batch_run_macros 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.
Run multiple macros in sequence. 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 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 MCP Server. 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 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.