set_pdf_metadata
AI agents use set_pdf_metadata 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.
The tool modifies metadata fields in PDF documents, which is a reversible write operation. While the description is empty, the tool name and server context clearly indicate it creates or updates metadata without deleting data or executing arbitrary code.
From the tool's definition Tool name 'set_pdf_metadata' indicates modification of PDF metadata. Sibling tools on this server include 'get_pdf_metadata' (read operation) and 'extract_pdf_images', 'merge_pdfs' (write operations), establishing context that this tool modifies document…
Attacks that exploit this kind of access
set_pdf_metadata. 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 set_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.
set_pdf_metadata 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 set_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 set_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.
set_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 →