compress_pdf_images
AI agents use compress_pdf_images to create or update resources in PDF Reader MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Reader MCP Server environment.
Based on the name, this tool likely compresses images within a PDF, which is a reversible modification (Write). The server context mentions optimization as a capability. With no description, confidence is reduced. Compression overwrites/modifies the PDF but is not necessarily irreversible if originals are preserved — however, lossy compression could be considered partially destructive.
From the tool's definition Tool name 'compress_pdf_images' and server description mentions 'optimization' capabilities. Description is empty, providing no further detail.
Attacks that exploit this kind of access
compress_pdf_images. It is categorised as a Write tool in the PDF Reader MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Reader MCP Server MCP server in PolicyLayer and add a rule for compress_pdf_images: 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 Reader MCP Server. Nothing to install.
compress_pdf_images 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 compress_pdf_images 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 compress_pdf_images. 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.
compress_pdf_images is provided by the PDF Reader MCP Server MCP server (lihongwen/pdfreadermcp). 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 →