Low Risk

extract_document

Extract raw text content from a document. Supports PDF (pdf-parse), Word/DOCX (mammoth), images via OCR (tesseract.js), Excel/CSV (xlsx), and plain text. Accepts a remote URL, a local file path, or base64-encoded bytes. Returns the extracted text plus character and word counts.

Accepts URL/endpoint input (url); Accepts file system path (file_path)

Part of the Docpulse MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call extract_document to retrieve information from Docpulse 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 extract_document 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.

nicholasemccormick-docpulse-mcp.yaml
tools:
  extract_document:
    rules:
      - action: allow

See the full Docpulse policy for all 4 tools.

Tool Name extract_document
Category Read
MCP Server Docpulse MCP Server
Risk Level Low

Agents calling read-class tools like extract_document have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the extract_document tool do? +

Extract raw text content from a document. Supports PDF (pdf-parse), Word/DOCX (mammoth), images via OCR (tesseract.js), Excel/CSV (xlsx), and plain text. Accepts a remote URL, a local file path, or base64-encoded bytes. Returns the extracted text plus character and word counts.. It is categorised as a Read tool in the Docpulse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract_document? +

Add a rule in your Intercept YAML policy under the tools section for extract_document. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docpulse MCP server.

What risk level is extract_document? +

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

Can I rate-limit extract_document? +

Yes. Add a rate_limit block to the extract_document rule in your Intercept 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 extract_document completely? +

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

extract_document is provided by the Docpulse MCP server (nicholasemccormick/docpulse-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.