Merge multiple PDFs into a single file
AI agents use merge_pdfs 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.
This tool creates a new combined document from existing inputs. It is a Write operation because it produces new data in a reversible manner. Severity is medium because misuse could result in unintended document combinations or potential exposure of sensitive information if the wrong PDFs are merged together, but the operation itself is not destructive (original files persist) and does not involve deletion, execution…
From the tool's definition Tool name is 'merge_pdfs' and description states 'Merge multiple PDFs into a single file'. The action combines existing PDFs into a new document, which is a reversible modification (the original files remain unaffected and the merged output can be deleted or…
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 MCP PDF, 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 PDFs into a single file. 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.
Register the MCP PDF 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 MCP PDF. 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 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.
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.