merge_pdfs
AI agents use merge_pdfs to create or update resources in PDF Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Tools MCP Server environment.
Merging PDFs creates a new combined file, which is a reversible write operation. The tool modifies/creates data but does not irreversibly delete (Destructive), execute arbitrary code (Execute), or handle financial transactions. Severity is low because PDF merging has limited blast radius—the result is a new file that can be deleted, and source files remain unchanged.
From the tool's definition Tool name 'merge_pdfs' indicates combining multiple PDF files. Server description states it enables 'merging...PDF files', confirming write-level data modification capability.
Attacks that exploit this kind of access
merge_pdfs. It is categorised as a Write tool in the PDF Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Tools 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 Tools 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 Tools MCP Server MCP server (lockon-n/pdf-tools-mcp). 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 →