AI agents use image_to_pdf 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.
Image-to-PDF conversion creates and writes new PDF files based on input images. This is a Write operation because it creates new data reversibly—the output PDF can be deleted or regenerated. It does not execute arbitrary code (Execute), destroy existing data (Destructive), move money (Financial), or retrieve data without modification (Read).
From the tool's definition Tool name 'image_to_pdf' indicates conversion of image files to PDF format, which creates new PDF documents.
Documented attack patterns abuse exactly the kind of access image_to_pdf 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 image_to_pdf:
{
"version": "1",
"default": "deny",
"tools": {
"image_to_pdf": {
"limits": [
{
"counter": "image_to_pdf_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} image_to_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.
image_to_pdf. 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 image_to_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 Co MCP Server. Nothing to install.
image_to_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 image_to_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 image_to_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.
image_to_pdf 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.