pdf_search_text
Search text inside a local PDF over selected pages. Returns page numbers and bounded snippets around matches. Deterministic, no network.
This record as markdown: /tools/io-github-homenshum-nodebench/pdf-search-text.md
What pdf_search_text does on Nodebench
AI agents call pdf_search_text to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pdf_search_text is rated Low
This tool only reads and searches content from an existing local PDF file, returning matching text snippets and page numbers. It has no side effects, does not modify data, execute code, delete content, or involve financial transactions. The deterministic, local-only operation further confirms its safe read-only nature. Classified as Read with low severity due to minimal blast radius if misused.
From the tool's definition Tool description states it 'Search[es] text inside a local PDF' and 'Returns page numbers and bounded snippets' — pure retrieval with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs pdf_search_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pdf_search_text, this is the rule to start with:
pdf_search_text is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every pdf_search_text call is checked against it from then on.
Questions about pdf_search_text
Search text inside a local PDF over selected pages. Returns page numbers and bounded snippets around matches. Deterministic, no network. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for pdf_search_text: 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 Nodebench. Nothing to install.
pdf_search_text is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pdf_search_text 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 pdf_search_text. 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.
pdf_search_text is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue