vba_pdm_operations · Solidworks MCP: Risk & Policy

WHAT IT DOES

What vba_pdm_operations does on Solidworks

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

VBA code generation for PDM vault operations can trigger execution of arbitrary VBA scripts that interact with SolidWorks PDM vaults, potentially modifying, moving, or deleting managed engineering documents. Even if it only generates (rather than executes) VBA, the output is executable code with broad system access. The PDM vault context means it could affect document lifecycle states, permissions, or data integrity.

From the tool's definition 'Generate VBA for PDM vault operations' — generates and likely executes VBA code targeting PDM (Product Data Management) vault operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vba_pdm_operations Rate-limited

vba_pdm_operations 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_pdm_operations": {
      "limits": [
        {
          "counter": "vba_pdm_operations_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_pdm_operations

What does the vba_pdm_operations tool do? +

Generate VBA for PDM vault 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_pdm_operations? +

Register the Solidworks MCP server in PolicyLayer and add a rule for vba_pdm_operations: 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_pdm_operations? +

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

Can I rate-limit vba_pdm_operations? +

Yes. Add a rate_limit block to the vba_pdm_operations 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_pdm_operations completely? +

Set action: deny in the PolicyLayer policy for vba_pdm_operations. 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_pdm_operations? +

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