create_feature_vba · Solidworks MCP: Risk & Policy

WHAT IT DOES

What create_feature_vba does on Solidworks

AI agents invoke create_feature_vba 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 create_feature_vba needs a policy

VBA code generation in a SolidWorks context implies execution of macros/scripts that can manipulate the CAD environment. VBA execution can trigger arbitrary operations within SolidWorks, including file modifications, system calls, and model changes. Even if it only generates (not runs) the code, the tool's purpose is to produce executable scripts, placing it in the Execute category.

From the tool's definition "Generate VBA code to create a specific feature" — generates and likely executes VBA code within SolidWorks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_feature_vba Rate-limited

create_feature_vba 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": {
    "create_feature_vba": {
      "limits": [
        {
          "counter": "create_feature_vba_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 create_feature_vba

What does the create_feature_vba tool do? +

Generate VBA code to create a specific feature. 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 create_feature_vba? +

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

What risk level is create_feature_vba? +

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

Can I rate-limit create_feature_vba? +

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

How do I block create_feature_vba completely? +

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

What MCP server provides create_feature_vba? +

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