AI agents call zemax_tde_summary to retrieve information from Zemax without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and displays tolerance operand data from Zemax OpticStudio's Tolerance Data Editor. It performs no modifications, deletions, or external operations — it simply retrieves and presents information. This is a classic Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'zemax_tde_summary' and description 'List the Tolerance Data Editor' indicate a retrieval/query operation. The verb 'List' and the context of 'summary' show the tool retrieves and displays existing tolerance data without modifying it.
Attacks that exploit this kind of access
List the Tolerance Data Editor: each operand's type, comment, and. It is categorised as a Read tool in the Zemax MCP Server, which means it retrieves data without modifying state.
Register the Zemax MCP server in PolicyLayer and add a rule for zemax_tde_summary: 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_tde_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the zemax_tde_summary 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_tde_summary. 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_tde_summary 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_tde_summary 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 →