Generate VBA for managing custom properties
AI agents invoke vba_custom_properties 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.
VBA (Visual Basic for Applications) generation for managing custom properties implies running macro/script code inside SolidWorks. Even if the tool only generates VBA code without directly executing it, VBA execution in CAD environments can modify documents, trigger operations, and cause unintended side effects. The 'managing' aspect also implies write operations.
From the tool's definition 'Generate VBA for managing custom properties' — generates and likely executes VBA code within SolidWorks
Attacks that exploit this kind of access
Generate VBA for managing custom properties. 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 vba_custom_properties: 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.
vba_custom_properties 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 vba_custom_properties 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 vba_custom_properties. 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.
vba_custom_properties 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 →