AI agents invoke open_pdf_preview to trigger actions in PDF MCP Server. 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.
Opening a PDF for preview triggers an external process or application, which goes beyond merely reading data. It executes a system-level action (launching a viewer). The description is sparse, lowering confidence slightly, but 'open' implies invoking an external operation rather than just querying data. Severity is medium as misuse could expose file contents or trigger unintended application launches.
From the tool's definition 'Open PDF file for preview' — triggers an external operation (opening a file in a viewer/preview application)
Documented attack patterns abuse exactly the kind of access open_pdf_preview gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for open_pdf_preview:
{
"version": "1",
"default": "deny",
"tools": {
"open_pdf_preview": {
"limits": [
{
"counter": "open_pdf_preview_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_pdf_preview 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.
Free to start. No card required.
Open PDF file for preview. It is categorised as a Execute tool in the PDF MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PDF MCP Server MCP server in PolicyLayer and add a rule for open_pdf_preview: 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 MCP Server. Nothing to install.
open_pdf_preview is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_pdf_preview 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.
Set action: deny in the PolicyLayer policy for open_pdf_preview. 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.
open_pdf_preview is provided by the PDF MCP Server MCP server (sohaib-2/pdf-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
22 PDF MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.