Medium Risk

split_pdf_by_pages

Split PDF into separate files by page ranges

How to control split_pdf_by_pages ↓

What split_pdf_by_pages does on MCP PDF

AI agents use split_pdf_by_pages to create or update resources in MCP PDF — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP PDF environment.

Medium Risk

Why split_pdf_by_pages needs a policy

This tool creates new PDF files by splitting an existing PDF into separate files based on page ranges. It is a Write operation as it creates new documents. The original PDF likely remains intact, making this reversible. Severity is medium as misuse could generate many unwanted files or expose document contents to wrong locations.

From the tool's definition Split PDF into separate files by page ranges

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

How to control split_pdf_by_pages

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 split_pdf_by_pages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "split_pdf_by_pages": {
      "limits": [
        {
          "counter": "split_pdf_by_pages_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

split_pdf_by_pages 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.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about split_pdf_by_pages

What does the split_pdf_by_pages tool do? +

Split PDF into separate files by page ranges. 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 split_pdf_by_pages? +

Register the MCP PDF MCP server in PolicyLayer and add a rule for split_pdf_by_pages: 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 split_pdf_by_pages? +

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

Can I rate-limit split_pdf_by_pages? +

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

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

split_pdf_by_pages 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.

Free to start. No card required.

46 MCP PDF tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.