AI agents invoke open_pdf_page to trigger actions in Pdf Navigator. 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.
This tool triggers an external operation — opening a PDF file in a viewer and navigating to a specific page. It interacts with an external PDF viewer application, which constitutes triggering an external operation rather than merely reading data. It's not purely destructive or financial, but it does execute an action in an external application.
From the tool's definition Open a PDF file to a specific page
Documented attack patterns abuse exactly the kind of access open_pdf_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pdf Navigator, and nothing reaches the server without passing your rules. This is the rule we recommend for open_pdf_page:
{
"version": "1",
"default": "deny",
"tools": {
"open_pdf_page": {
"limits": [
{
"counter": "open_pdf_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_pdf_page 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 a PDF file to a specific page. It is categorised as a Execute tool in the Pdf Navigator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pdf Navigator MCP server in PolicyLayer and add a rule for open_pdf_page: 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 Navigator. Nothing to install.
open_pdf_page 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_page 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_page. 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_page is provided by the Pdf Navigator MCP server (matsengrp/pdf-navigator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pdf Navigator, 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.
7 Pdf Navigator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.