Export a recorded macro to VBA code
AI agents call macro_export_vba to retrieve information from Solidworks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool exports (reads/retrieves) an already-recorded macro and converts it to VBA code. This is a read/export operation that retrieves existing data rather than executing code or modifying state. Severity is low as it only outputs code text without running it.
From the tool's definition Export a recorded macro to VBA code
Attacks that exploit this kind of access
Export a recorded macro to VBA code. It is categorised as a Read tool in the Solidworks MCP Server, which means it retrieves data without modifying state.
Register the Solidworks MCP server in PolicyLayer and add a rule for macro_export_vba: 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.
macro_export_vba is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the macro_export_vba 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_export_vba. 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_export_vba 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 →