zemax_quick_focus · Zemax MCP: Risk & Policy

WHAT IT DOES

What zemax_quick_focus does on Zemax

AI agents invoke zemax_quick_focus 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_quick_focus needs a policy

This tool triggers an external optical analysis and optimization operation within Zemax OpticStudio whose effects depend on the current design state. While it modifies design parameters (back focal distance), the modification is tied to the execution of an algorithm rather than being a direct data write. The effects are reversible (can be undone or re-run), so it does not qualify as Destructive.

From the tool's definition Tool description states 'Run Quick Focus (adjusts back focal distance to minimize the spot/RMS)' — the verb 'Run' combined with 'adjusts' indicates it executes an optical simulation/optimization operation that modifies optical design parameters (back focal…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zemax_quick_focus Rate-limited

zemax_quick_focus 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_quick_focus": {
      "limits": [
        {
          "counter": "zemax_quick_focus_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_quick_focus

What does the zemax_quick_focus tool do? +

Run Quick Focus (adjusts back focal distance to minimize the spot/RMS). 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_quick_focus? +

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

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

Can I rate-limit zemax_quick_focus? +

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

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

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