zemax_disconnect · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_disconnect does on Zemax

AI agents use zemax_disconnect to create or update resources in Zemax — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zemax environment.

WHY IT NEEDS A POLICY

Why zemax_disconnect needs a policy

An AI agent can call zemax_disconnect faster than any human can review — one bad instruction and it creates or modifies resources in Zemax by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_disconnect Rate-limited

zemax_disconnect stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_disconnect": {
      "limits": [
        {
          "counter": "zemax_disconnect_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_disconnect

What does the zemax_disconnect tool do? +

Drop the ZOS-API connection. In standalone mode this closes the headless process. It is categorised as a Write tool in the Zemax MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zemax_disconnect? +

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

zemax_disconnect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zemax_disconnect? +

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

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

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

// THE FULL RECORD

zemax_disconnect is one line of Zemax's registry record.

The record carries the whole server: 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 →