AI agents use pdf_split to create or update resources in PDF Co MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Co MCP Server environment.
PDF splitting reads an existing PDF and writes new PDF file(s) containing subsets of pages. This is categorized as Write because it creates new data artifacts in a reversible manner. It is not Read-only (produces new outputs), not Execute (doesn't run arbitrary code based on arguments), not Destructive (original file is not deleted, operation is reversible), and not Financial.
From the tool's definition Tool name 'pdf_split' indicates a PDF manipulation operation. The sibling tools on this server (csv_to_pdf, document_to_pdf, excel_to_pdf, create_fillable_forms) establish the context as PDF processing and modification tasks.
Documented attack patterns abuse exactly the kind of access pdf_split gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Co MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for pdf_split:
{
"version": "1",
"default": "deny",
"tools": {
"pdf_split": {
"limits": [
{
"counter": "pdf_split_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pdf_split 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.
Free to start. No card required.
pdf_split. It is categorised as a Write tool in the PDF Co MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Co MCP Server MCP server in PolicyLayer and add a rule for pdf_split: 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 PDF Co MCP Server. Nothing to install.
pdf_split is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pdf_split 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 pdf_split. 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.
pdf_split is provided by the PDF Co MCP Server MCP server (pdfdotco/pdfco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF Co MCP Server, 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.
38 PDF Co MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.