Open a macro in the SolidWorks VBA editor
AI agents invoke edit_macro 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.
Opening a macro in the VBA editor is a precursor to executing arbitrary VBA code within SolidWorks. Even if the tool itself only 'opens' the editor, it enables code execution in the SolidWorks environment. VBA macros can perform destructive, system-level, or arbitrary operations, making this an Execute-category tool with high severity.
From the tool's definition 'Open a macro in the SolidWorks VBA editor' — the tool interacts with the VBA macro editor, which is used to run/edit executable code within SolidWorks
Attacks that exploit this kind of access
Open a macro in the SolidWorks VBA editor. 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 edit_macro: 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.
edit_macro 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 edit_macro 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 edit_macro. 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.
edit_macro 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 →