remove_pdf_metadata
AI agents call remove_pdf_metadata to permanently remove resources in PDF Reader MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name strongly suggests it removes (deletes) metadata from a PDF, which is likely an irreversible operation. Removing metadata cannot be easily undone without a backup. The description is empty, which lowers confidence slightly, but the name is unambiguous enough to classify as Destructive. Severity is medium since metadata loss, while irreversible, does not affect the core content of the PDF.
From the tool's definition Tool name 'remove_pdf_metadata' implies irreversible removal of metadata from a PDF file.
Attacks that exploit this kind of access
remove_pdf_metadata. It is categorised as a Destructive tool in the PDF Reader MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PDF Reader MCP Server MCP server in PolicyLayer and add a rule for remove_pdf_metadata: 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.
remove_pdf_metadata is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_pdf_metadata 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 remove_pdf_metadata. 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.
remove_pdf_metadata 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 →