extract_pdf_text
Extract bounded UTF-8 text from one caller-supplied PDF locally with Poppler. Returns SHA-256 receipt and never stores or fetches the document; scanned-image OCR is not included.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/extract-pdf-text.md
What extract_pdf_text does on Delx Mcp A2a
AI agents call extract_pdf_text to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
max_chars | integer | — | |
pdf_base64 | string | Yes | One base64-encoded PDF up to 4 MiB decoded; application/pdf data URIs are accepted. |
file_base64 | string | — | Alias for pdf_base64. |
Parameters from the server's own tool schema.
Why extract_pdf_text is rated Low
This tool performs document text extraction, which is inherently a read operation. It retrieves content from a caller-supplied PDF using Poppler (a PDF rendering library) and returns a SHA-256 receipt for integrity verification. The explicit guarantee that it 'never stores or fetches' indicates no persistence or external data access, eliminating Write and Destructive categories.
From the tool's definition Tool description explicitly states it 'Extract[s]' text from a PDF and 'never stores or fetches the document' — a read-only operation with no side effects. The function is data retrieval (extract) without modification, creation, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs extract_pdf_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For extract_pdf_text, this is the rule to start with:
extract_pdf_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 Delx Mcp A2a, apply this rule, and every extract_pdf_text call is checked against it from then on.
Questions about extract_pdf_text
Extract bounded UTF-8 text from one caller-supplied PDF locally with Poppler. Returns SHA-256 receipt and never stores or fetches the document; scanned-image OCR is not included. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
extract_pdf_text accepts 3 parameters: max_chars, pdf_base64, file_base64. Required: pdf_base64. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for extract_pdf_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 Delx Mcp A2a. Nothing to install.
extract_pdf_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 extract_pdf_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 extract_pdf_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.
extract_pdf_text is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue