zemax_run_tolerancing · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_run_tolerancing does on Zemax

AI agents invoke zemax_run_tolerancing to trigger actions in Zemax. 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 zemax_run_tolerancing needs a policy

This tool executes a non-trivial simulation (Monte Carlo tolerancing analysis) whose computational effects and side effects depend on the current state of the optical design and tolerances. While not destructive to the design itself, it initiates an external operation (Monte Carlo simulation) that consumes resources and modifies the analysis state.

From the tool's definition Tool name contains 'run' and description states 'Run a Monte Carlo tolerancing analysis', indicating execution of a computational operation. This triggers simulation/analysis on optical design data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_run_tolerancing Rate-limited

zemax_run_tolerancing 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": {
    "zemax_run_tolerancing": {
      "limits": [
        {
          "counter": "zemax_run_tolerancing_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 Zemax, so you can run agents against it safely.

FAQ

Questions about zemax_run_tolerancing

What does the zemax_run_tolerancing tool do? +

Run a Monte Carlo tolerancing analysis over the current TDE tolerances. It is categorised as a Execute tool in the Zemax MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on zemax_run_tolerancing? +

Register the Zemax MCP server in PolicyLayer and add a rule for zemax_run_tolerancing: 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 Zemax. Nothing to install.

What risk level is zemax_run_tolerancing? +

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

Can I rate-limit zemax_run_tolerancing? +

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

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

zemax_run_tolerancing is provided by the Zemax MCP server (webworn/zemax-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.