PDF Tools

PDF Secure Redaction Sanitizer

Permanently remove PDF text and hidden page objects by rebuilding an image-only PDF.

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/pdf-secure-redaction-sanitizer' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"sourceFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/pdf-secure-redaction-sanitizer' \
  -F 'sourceFile=/public/processing/smoke-test-document.pdf' \
  -F 'redactionRects=[{"page":1,"x":35,"y":210,"width":300,"height":36,"label":"REDACTED"}]' \
  -F 'dpi=144' \
  -F 'includeLabel=true' \
  -F 'redactionColor=#000000'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/pdf-secure-redaction-sanitizer

Parameters

Name	Type	Required	Description
sourceFile	fileupload required	Yes	—
redactionRects	textarea	Yes	—
dpi	number	No	Higher DPI improves visual fidelity but increases CPU and output size.
includeLabel	checkbox	No	—
redactionColor	color	No	—

File-type parameters must be uploaded first via POST /upload/pdf-secure-redaction-sanitizer, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-pdf-secure-redaction-sanitizer": {
      "name": "pdf-secure-redaction-sanitizer",
      "description": "Permanently remove PDF text and hidden page objects by rebuilding an image-only PDF.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=pdf-secure-redaction-sanitizer",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "pdf-secure-redaction-sanitizer",
    "arguments": {
  "sourceFile": "/public/processing/smoke-test-document.pdf",
  "redactionRects": "[{\"page\":1,\"x\":35,\"y\":210,\"width\":300,\"height\":36,\"label\":\"REDACTED\"}]",
  "dpi": 144,
  "includeLabel": true,
  "redactionColor": "#000000"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]