Merge multiple PDF files into a single PDF. All paths must be absolute paths on the user
AI agents use merge_pdfs to create or update resources in PDF Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Tools environment.
Merging PDFs creates new data (the merged file) and modifies the logical structure of existing documents into a new artifact. This is a reversible write operation: the merged result can be deleted or regenerated, and the source files remain untouched. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Merge multiple PDF files into a single PDF' — this creates a new combined document by modifying/combining existing data into a new output.
Documented attack patterns abuse exactly the kind of access merge_pdfs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for merge_pdfs:
{
"version": "1",
"default": "deny",
"tools": {
"merge_pdfs": {
"limits": [
{
"counter": "merge_pdfs_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_pdfs 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.
Merge multiple PDF files into a single PDF. All paths must be absolute paths on the user. It is categorised as a Write tool in the PDF Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Tools MCP server in PolicyLayer and add a rule for merge_pdfs: 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 Tools. Nothing to install.
merge_pdfs 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 merge_pdfs 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 merge_pdfs. 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.
merge_pdfs is provided by the PDF Tools MCP server (open-document-alliance/pdf-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 PDF Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 PDF Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.