Split a PDF into separate files. Extract specific pages or split into individual page files.
AI agents use pdf_split to create or update resources in Mcp Pdf Utils — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pdf Utils environment.
pdf_split creates new files by extracting and organizing pages from an existing PDF. This is fundamentally a Write operation: it produces new data (separate PDF files) without irreversibly destroying the original data. The operation is reversible—the original PDF remains intact and the newly created files can be deleted.
From the tool's definition Tool description states 'Split a PDF into separate files. Extract specific pages or split into individual page files.' The operation creates new PDF files from an existing PDF, which is a reversible write operation.
Attacks that exploit this kind of access
Split a PDF into separate files. Extract specific pages or split into individual page files. It is categorised as a Write tool in the Mcp Pdf Utils MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Pdf Utils 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 Mcp Pdf Utils. 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 Mcp Pdf Utils MCP server (zekovdev/mcp-pdf-utils). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →