navigate_file_dialog · MacWright MCP: Risk & Policy

WHAT IT DOES

What navigate_file_dialog does on MacWright

AI agents invoke navigate_file_dialog to trigger actions in MacWright. 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 navigate_file_dialog needs a policy

This tool executes browser-like actions (UI automation) that manipulate system dialogs and can trigger side effects through user interactions. It's not merely reading state (Read), nor is it reversibly creating/modifying data (Write). It actively navigates dialogs which can lead to file operations, downloads, or other system-level effects.

From the tool's definition Tool directly navigates and controls macOS file dialogs, triggering external UI interactions. Description states it 'Navigate[s] a macOS file open/save dialog' - a direct action on the system that changes application state and can trigger file operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_file_dialog Rate-limited

navigate_file_dialog 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": {
    "navigate_file_dialog": {
      "limits": [
        {
          "counter": "navigate_file_dialog_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 MacWright, so you can run agents against it safely.

FAQ

Questions about navigate_file_dialog

What does the navigate_file_dialog tool do? +

Navigate a macOS file open/save dialog to a specific path. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate_file_dialog? +

Register the MacWright MCP server in PolicyLayer and add a rule for navigate_file_dialog: 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 MacWright. Nothing to install.

What risk level is navigate_file_dialog? +

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

Can I rate-limit navigate_file_dialog? +

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

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

navigate_file_dialog is provided by the MacWright MCP server (ruchit-p/macwright). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.