AI agents use zemax_set_wavelengths 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.
The tool modifies design parameters (wavelengths) reversibly; this is a configuration change, not a destructive deletion. An AI agent misusing this could alter optical simulations causing incorrect design iterations, but the change can be undone by setting wavelengths again.
From the tool's definition Tool description states 'Replace the wavelength set with the given values' — a modification operation that updates optical design parameters in Zemax OpticStudio.
Attacks that exploit this kind of access
Replace the wavelength set with the given values (in micrometers). 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.
Register the Zemax MCP server in PolicyLayer and add a rule for zemax_set_wavelengths: 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.
zemax_set_wavelengths is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zemax_set_wavelengths 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.
Set action: deny in the PolicyLayer policy for zemax_set_wavelengths. 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.
zemax_set_wavelengths 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.
zemax_set_wavelengths 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 →