convert_text_to_native_macro · Solidworks MCP: Risk & Policy

WHAT IT DOES

What convert_text_to_native_macro does on Solidworks

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

This tool takes arbitrary VBA code and converts/initializes it into a runnable SolidWorks macro. While the tool itself may be a preparation step, it enables execution of arbitrary VBA code within SolidWorks, which can perform any operation including destructive ones.

From the tool's definition 'Convert plain text VBA code to a properly initialized SolidWorks macro' — converts and initializes VBA macro code for execution in SolidWorks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_text_to_native_macro Rate-limited

convert_text_to_native_macro 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": {
    "convert_text_to_native_macro": {
      "limits": [
        {
          "counter": "convert_text_to_native_macro_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 convert_text_to_native_macro

What does the convert_text_to_native_macro tool do? +

Convert plain text VBA code to a properly initialized SolidWorks macro. 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 convert_text_to_native_macro? +

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

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

Can I rate-limit convert_text_to_native_macro? +

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

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

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