// MCP TOOL REFERENCE

reveal_in_finder

ServerPDF Tools
CategoryExecute

WHAT REVEAL_IN_FINDER ON PDF TOOLS DOES

AI agents invoke reveal_in_finder to trigger actions in PDF Tools. 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.

THE RISK

High Risk

This tool triggers an external OS-level operation (launching/focusing the file manager application) rather than simply reading or writing data. It executes a system action to open Finder/Explorer and reveal a file. While the blast radius is low (it only opens a UI window), it is an external operation execution, not a passive read.

From the tool's definition Open the OS file manager with the given file selected... macOS: Finder → Reveal; Windows: Explorer → select; Linux: opens the enclosing folder

Documented attack patterns abuse exactly the kind of access reveal_in_finder gives an agent:

HOW TO CONTROL REVEAL_IN_FINDER

PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for reveal_in_finder:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reveal_in_finder": {
      "limits": [
        {
          "counter": "reveal_in_finder_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register PDF Tools — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More PDF Tools tools

Write reorder_pdf_pages Rearrange the pages of a PDF in a new order. All pages must be included exactly once (stri Write rotate_pdf_pages Rotate pages in a PDF by 90, 180, or 270 degrees. All paths must be absolute paths on the Write split_pdf Split a PDF into multiple files by page ranges (e.g. Write add_signature_field Draw a visible Write apply_page_plan Apply a page plan to a PDF: reorder, rotate, and delete pages in one pass. Pages not liste Write apply_text Stamp a plain text string at a location on a PDF, saving the result as a new file. Use thi Write bulk_fill_from_csv Fill multiple PDFs using data from a CSV file Write create_signature Save a reusable signature the user can apply to PDFs. Two styles:

All 36 PDF Tools tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in PDF Tools → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the reveal_in_finder tool do? +

Open the OS file manager with the given file selected (macOS: Finder → Reveal; Windows: Explorer → select; Linux: opens the enclosing folder). Used by the viewer to surface the active PDF or its backup so the user can immediately see the relevant file. It is categorised as a Execute tool in the PDF Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reveal_in_finder? +

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

What risk level is reveal_in_finder? +

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

Can I rate-limit reveal_in_finder? +

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

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

reveal_in_finder is provided by the PDF Tools MCP server (open-document-alliance/pdf-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PDF Tools tool call.

Deterministic rules across all 36 PDF Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN PDF TOOLS →

Free to start. No card required.

36 PDF Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

reveal_in_finder

// WHAT REVEAL_IN_FINDER ON PDF TOOLS DOES

// THE RISK

// HOW TO CONTROL REVEAL_IN_FINDER

// EXPLORE