Encrypts a PDF document from base64 string or a remote URL.
AI agents use encrypt_document to create or update resources in PDF Generator API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Generator API MCP Server environment.
Encryption is a reversible modification to document metadata/properties rather than an irreversible deletion. While the encrypted document cannot be accessed without the key, the operation itself is non-destructive and can theoretically be reversed (by decryption). This places it in the Write category.
From the tool's definition The tool description states it "Encrypts a PDF document", which modifies an existing document's properties reversibly.
Attacks that exploit this kind of access
Encrypts a PDF document from base64 string or a remote URL. It is categorised as a Write tool in the PDF Generator API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Generator API MCP Server MCP server in PolicyLayer and add a rule for encrypt_document: 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 Generator API MCP Server. Nothing to install.
encrypt_document 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_document 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_document. 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_document is provided by the PDF Generator API MCP Server MCP server (pdfgeneratorapi/mcp-server). 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 →