zemax_mce_add_operand · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_mce_add_operand does on Zemax

AI agents use zemax_mce_add_operand 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_mce_add_operand needs a policy

This tool creates or modifies optimization operands in Zemax's Merit Cycle Editor, which are constraints used in optical design optimization. While reversible (operands can be removed), it modifies the optical system configuration and affects design behavior. The empty description reduces confidence slightly, but the naming pattern and server context indicate a Write-category modification tool.

From the tool's definition Tool name 'zemax_mce_add_operand' combines 'add' (Write operation) with 'mce' (Zemax Merit Cycle Editor) and 'operand' (optimization constraint). The 'add' verb indicates creation/insertion of a new operand into an optimization configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_mce_add_operand Rate-limited

zemax_mce_add_operand 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_mce_add_operand": {
      "limits": [
        {
          "counter": "zemax_mce_add_operand_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_mce_add_operand

What does the zemax_mce_add_operand tool do? +

zemax_mce_add_operand. 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_mce_add_operand? +

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

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

Can I rate-limit zemax_mce_add_operand? +

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

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

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