// SCAN REPORT

Zemax

31 tools. 24 can modify or destroy data without limits.

24 write tools that can modify data. Rate limits recommended.

Last updated: 7 Jul 2026

24 can modify or destroy data

7 read-only

31 tools total

Community server · catalogue entry checked 07/07/2026

How to control Zemax ↓

TOOL MAP

What Zemax exposes to your agents

Read (7) Write / Execute (24) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Zemax tools

Execute · High zemax_merit_wizard This tool executes an automated optimization workflow in Zemax OpticStudio. Execute · Medium zemax_quick_focus This tool triggers an external optical analysis and optimization operation within Zemax OpticStudio whose effects depend on the current design state. Execute · High zemax_run_analysis This tool executes analysis operations within Zemax OpticStudio, a specialized engineering simulation environment. Execute · High zemax_run_tolerancing 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.

24 of Zemax's 31 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zemax

PolicyLayer is an MCP gateway — it sits between your AI agents and Zemax, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "zemax_analysis_series": {
    "limits": [
      {
        "counter": "zemax_analysis_series_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "zemax_info": {
    "limits": [
      {
        "counter": "zemax_info_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zemax — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZEMAX →

Instant setup, no code required.

FULL CATALOGUE

All 31 Zemax tools

EXECUTE 9 tools

Execute zemax_batch_ray_trace zemax_batch_ray_trace Execute zemax_eval zemax_eval Execute zemax_merit_wizard Run the Optimization (Merit Function) Wizard to build a default merit function. Execute zemax_new_system Start a new, empty optical system. sequential=False starts in non-sequential mode. Execute zemax_nsc_ray_trace zemax_nsc_ray_trace Execute zemax_optimize zemax_optimize Execute zemax_quick_focus Run Quick Focus (adjusts back focal distance to minimize the spot/RMS). Execute zemax_run_analysis zemax_run_analysis Execute zemax_run_tolerancing Run a Monte Carlo tolerancing analysis over the current TDE tolerances.

WRITE 15 tools

Write zemax_analysis_series zemax_analysis_series Write zemax_connect zemax_connect Write zemax_disconnect Drop the ZOS-API connection. In standalone mode this closes the headless process. Write zemax_lde_insert_surface Insert a new surface at the given 0-based position in the Lens Data Editor. Write zemax_lde_set_surface Edit a surface (0-based index). Any omitted parameter is left unchanged. Write zemax_mce_add_config Add a new configuration (column) to the MCE. with_pickups=True links the new Write zemax_mce_add_operand zemax_mce_add_operand Write zemax_open_file Open a .zmx / .zos lens file (Windows path). Write zemax_save_file Save the current system. If path is given, Save-As to that path. Write zemax_set_aperture Set the System Aperture. Write zemax_set_fields Set field points. field_type is 'Angle', 'ObjectHeight', 'ParaxialImageHeight', Write zemax_set_variable Make a Lens Data cell a VARIABLE for optimization. cell is 'radius', Write zemax_set_wavelengths Replace the wavelength set with the given values (in micrometers). Write zemax_spot_rms Compute the RMS spot radius per field via a Spot Diagram analysis (quick metric). Write zemax_tolerance_wizard Build a default tolerance set via the Tolerancing Wizard (radius, thickness,

READ 7 tools

Read zemax_info Report the current connection: mode, license edition, serial, open file, seq/nonseq. Read zemax_lde_summary Return a compact table of every surface: index, comment, radius, thickness, Read zemax_mce_summary List the Multi-Configuration Editor: number of configurations, and for each Read zemax_merit_value Return the current merit function value (lower is better). Read zemax_nsc_detector_data zemax_nsc_detector_data Read zemax_nsc_summary List Non-Sequential Component Editor objects: index, type, comment, material. Read zemax_tde_summary List the Tolerance Data Editor: each operand's type, comment, and

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Zemax

How do I prevent bulk modifications through Zemax? +

The Zemax server has 15 write tools including zemax_analysis_series, zemax_connect, zemax_disconnect. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Zemax.

How many tools does the Zemax MCP server expose? +

31 tools across 3 categories: Execute, Read, Write. 7 are read-only. 24 can modify, create, or delete data.

How do I enforce a policy on Zemax? +

Register the Zemax MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zemax tool call.

Deterministic rules across all 31 Zemax tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZEMAX →

Instant setup, no code required.

31 Zemax tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Zemax's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →