AI agents use encrypt_pdf 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.
Encrypting a PDF modifies the file by applying encryption, which is a reversible write operation (the file can be decrypted). However, if it overwrites the original file without backup, it could be considered destructive. Since a sibling tool 'decrypt_pdf' exists, encryption appears reversible, placing this in Write. Severity is high because misuse could lock users out of their own files or corrupt access.
From the tool's definition Tool name 'encrypt_pdf'; server description mentions 'encrypting PDFs' as a core operation. Description is empty.
Documented attack patterns abuse exactly the kind of access encrypt_pdf 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 encrypt_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"encrypt_pdf": {
"limits": [
{
"counter": "encrypt_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}encrypt_pdf 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.
encrypt_pdf. 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 encrypt_pdf: 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.
encrypt_pdf 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 encrypt_pdf 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 encrypt_pdf. 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.
encrypt_pdf 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.