zemax_nsc_ray_trace · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_nsc_ray_trace does on Zemax

AI agents invoke zemax_nsc_ray_trace to trigger actions in Zemax. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why zemax_nsc_ray_trace needs a policy

Based on the tool name and server context, this tool likely executes a Non-Sequential Component (NSC) ray trace simulation in Zemax OpticStudio, which is a computational operation that triggers external processing. Sibling tools like 'zemax_batch_ray_trace' and 'zemax_eval' confirm this server pattern of executing operations in OpticStudio.

From the tool's definition Tool name 'zemax_nsc_ray_trace' suggests running a non-sequential ray trace simulation in OpticStudio; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_nsc_ray_trace Rate-limited

zemax_nsc_ray_trace stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_nsc_ray_trace": {
      "limits": [
        {
          "counter": "zemax_nsc_ray_trace_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_nsc_ray_trace

What does the zemax_nsc_ray_trace tool do? +

zemax_nsc_ray_trace. It is categorised as a Execute tool in the Zemax MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on zemax_nsc_ray_trace? +

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

zemax_nsc_ray_trace is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit zemax_nsc_ray_trace? +

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

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

zemax_nsc_ray_trace 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_nsc_ray_trace 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 →