macro_set_security · Solidworks MCP: Risk & Policy

WHAT IT DOES

What macro_set_security does on Solidworks

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

Setting macro security level is an Execute-class action: it changes a system-level security policy that governs whether and which macros can run. Lowering macro security could allow malicious macros to execute, making misuse high-severity. It is not purely Write because it directly affects code execution permissions, and not Destructive since it doesn't irreversibly delete data.

From the tool's definition 'Attempt to set macro security level' — modifies the macro security configuration of SolidWorks, controlling what macros are permitted to run

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

macro_set_security Rate-limited

macro_set_security 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": {
    "macro_set_security": {
      "limits": [
        {
          "counter": "macro_set_security_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 macro_set_security

What does the macro_set_security tool do? +

Attempt to set macro security level. 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 macro_set_security? +

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

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

Can I rate-limit macro_set_security? +

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

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

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