AI agents use pdf_merge 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 merging is a write operation—it creates a new combined PDF file by modifying/reorganizing content from source PDFs. It is reversible (the original files remain, and the merged result can be deleted or regenerated), so it does not qualify as Destructive.
From the tool's definition Tool name 'pdf_merge' indicates it combines PDF files into a single document, modifying the output structure. The empty description limits certainty, but merging is a reversible write operation that creates new data by combining existing files.
Documented attack patterns abuse exactly the kind of access pdf_merge 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_merge:
{
"version": "1",
"default": "deny",
"tools": {
"pdf_merge": {
"limits": [
{
"counter": "pdf_merge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pdf_merge 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_merge. 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_merge: 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_merge 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_merge 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_merge. 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_merge 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.