AI agents use merge_pdfs to create or update resources in PDF MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF MCP Server environment.
Merging PDFs creates a new file by combining existing files—a write operation that modifies the file system and creates new data. While reversible (the original files typically remain and the merge can be undone by deleting the output), it falls under Write rather than Read (it doesn't just retrieve data) or Destructive (it doesn't irreversibly delete or overwrite existing files).
From the tool's definition Tool description states 'Merge multiple PDF files into one', which creates a new combined PDF file. This is a reversible modification operation.
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 MCP Server, 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 one. It is categorised as a Write tool in the PDF MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF MCP Server 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 MCP Server. 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 MCP Server MCP server (sohaib-2/pdf-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF 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.
22 PDF MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.