diagnose_macro_execution · Solidworks MCP: Risk & Policy

WHAT IT DOES

What diagnose_macro_execution does on Solidworks

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

The tool name and description reference 'macro execution', which implies running macros (code/scripts) within SolidWorks. Even framed as diagnostics, executing macros constitutes running code with potentially broad side effects. 'Diagnose' suggests it triggers execution to observe behavior, making Execute the appropriate category.

From the tool's definition diagnose macro execution issues with detailed logging

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_macro_execution Rate-limited

diagnose_macro_execution 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": {
    "diagnose_macro_execution": {
      "limits": [
        {
          "counter": "diagnose_macro_execution_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 diagnose_macro_execution

What does the diagnose_macro_execution tool do? +

Diagnose macro execution issues with detailed logging. 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 diagnose_macro_execution? +

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

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

Can I rate-limit diagnose_macro_execution? +

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

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

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