zemax_run_analysis · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_run_analysis does on Zemax

AI agents invoke zemax_run_analysis 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_run_analysis needs a policy

This tool executes analysis operations within Zemax OpticStudio, a specialized engineering simulation environment. While the description is empty (limiting confidence slightly), the name and sibling tool patterns ('run_', 'batch_', 'eval_') confirm this performs computational execution rather than simple data retrieval.

From the tool's definition Tool name 'zemax_run_analysis' combined with server context ('drive your optical designs from intent to result') and sibling tools like 'zemax_analysis_series', 'zemax_batch_ray_trace', 'zemax_eval' indicate execution of computational operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_run_analysis Rate-limited

zemax_run_analysis 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_run_analysis": {
      "limits": [
        {
          "counter": "zemax_run_analysis_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_run_analysis

What does the zemax_run_analysis tool do? +

zemax_run_analysis. 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_run_analysis? +

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

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

Can I rate-limit zemax_run_analysis? +

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

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

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