Low Risk

pdf_search

Search text across a PDF and return matches with a short surrounding snippet and the page number. The query is matched as a literal substring (case-insensitive by default). Searches all pages unless a range is given.

Risk signalsAccepts file system path (filePath) · Accepts freeform code/query input (query)

Part of the Pdf Toolkit server.

pdf_search is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PDF TOOLKIT →

Free to start. No card required.

AI agents call pdf_search to retrieve information from Pdf Toolkit without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though pdf_search only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pdf_search": {}
  }
}

See the full Pdf Toolkit policy for all 22 tools.

Get this rule live on your own Pdf Toolkit server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PDF TOOLKIT →

View all 22 tools →

These attack patterns abuse exactly the kind of access pdf_search gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so pdf_search only ever does what you allow.

SECURE PDF TOOLKIT →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the pdf_search tool do? +

Search text across a PDF and return matches with a short surrounding snippet and the page number. The query is matched as a literal substring (case-insensitive by default). Searches all pages unless a range is given.. It is categorised as a Read tool in the Pdf Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pdf_search? +

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

What risk level is pdf_search? +

pdf_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pdf_search? +

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

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

pdf_search is provided by the Pdf Toolkit MCP server (@aryanbv/pdf-toolkit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pdf Toolkit tool call.

Deterministic rules across all 22 Pdf Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.