AI agents call zemax_nsc_detector_data 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.
Based on naming convention and peer tools on the server, this appears to be a data retrieval function that queries detector output from optical simulations. No side effects or modifications are evident. The empty description reduces confidence, but the context strongly suggests a Read operation. Even if it extracts simulation data, this is non-destructive and consistent with optical analysis workflows.
From the tool's definition Tool name 'zemax_nsc_detector_data' contains 'data' suffix and appears in a series of analysis/query tools (zemax_analysis_series, zemax_batch_ray_trace, zemax_info, zemax_lde_summary). No description provided.
Attacks that exploit this kind of access
zemax_nsc_detector_data. 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_nsc_detector_data: 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_nsc_detector_data 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_nsc_detector_data 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_nsc_detector_data. 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_nsc_detector_data 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_nsc_detector_data 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 →