repair_pdf

THE RISK

Medium Risk

Why repair_pdf needs a policy

Repairing a PDF modifies/rewrites the file to fix corruption. This is a reversible write operation (the original damaged file is overwritten with a repaired version), not a destructive deletion. Severity is medium because it modifies existing files, potentially altering content in the process.

From the tool's definition repair corrupted or damaged PDF files

Documented attack patterns abuse exactly the kind of access repair_pdf gives an agent:

POLICY

How to control repair_pdf

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP PDF, and nothing reaches the server without passing your rules. This is the rule we recommend for repair_pdf:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "repair_pdf": {
      "limits": [
        {
          "counter": "repair_pdf_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

repair_pdf stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register MCP PDF — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP PDF tools

Write optimize_pdf Optimize PDF file size and performance Write reorder_pdf_pages Reorder pages in a PDF document Write rotate_pages Rotate specific pages by 90, 180, or 270 degrees Write split_pdf Split PDF into multiple files at specified pages Write split_pdf_by_bookmarks Split PDF into separate files using bookmarks as breakpoints Write split_pdf_by_pages Split PDF into separate files by page ranges Write add_date_field Add a date field with format validation to PDF Write add_field_validation Add validation rules to existing form fields

All 46 MCP PDF tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about repair_pdf

What does the repair_pdf tool do? +

Attempt to repair corrupted or damaged PDF files. It is categorised as a Write tool in the MCP PDF MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on repair_pdf? +

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

What risk level is repair_pdf? +

repair_pdf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit repair_pdf? +

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

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

repair_pdf is provided by the MCP PDF MCP server (rsp2k/mcp-pdf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP PDF tool call.

Start from MCP PDF, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →