vba_surface_modeling · Solidworks MCP: Risk & Policy

WHAT IT DOES

What vba_surface_modeling does on Solidworks

AI agents invoke vba_surface_modeling 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.

WHY IT NEEDS A POLICY

Why vba_surface_modeling needs a policy

VBA code generation implies execution of arbitrary scripting within the SolidWorks environment. VBA macros can perform a wide range of operations including file I/O, model manipulation, and system calls. If the generated VBA is automatically executed (likely given the MCP context), this is an Execute-category tool with high severity due to the broad blast radius of arbitrary VBA execution.

From the tool's definition 'Generate VBA for surface modeling operations' — generates and presumably executes VBA (Visual Basic for Applications) code within SolidWorks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vba_surface_modeling Rate-limited

vba_surface_modeling 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vba_surface_modeling": {
      "limits": [
        {
          "counter": "vba_surface_modeling_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Solidworks, so you can run agents against it safely.

FAQ

Questions about vba_surface_modeling

What does the vba_surface_modeling tool do? +

Generate VBA for surface modeling operations. 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.

How do I enforce a policy on vba_surface_modeling? +

Register the Solidworks MCP server in PolicyLayer and add a rule for vba_surface_modeling: 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.

What risk level is vba_surface_modeling? +

vba_surface_modeling is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vba_surface_modeling? +

Yes. Add a rate_limit block to the vba_surface_modeling 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.

How do I block vba_surface_modeling completely? +

Set action: deny in the PolicyLayer policy for vba_surface_modeling. 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.

What MCP server provides vba_surface_modeling? +

vba_surface_modeling 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.