add_pdf_content
AI agents use add_pdf_content to create or update resources in oxidize-pdf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your oxidize-pdf MCP Server environment.
The tool name 'add_pdf_content' suggests it adds or inserts content into a PDF document, which is a reversible modification operation (Write category). This aligns with the broader PDF manipulation capabilities shown by sibling tools. Severity is medium because modifying PDFs could corrupt documents or introduce unintended content, but changes are typically reversible via undo or re-processing.
From the tool's definition Tool name 'add_pdf_content' combined with sibling tools including 'create_pdf', 'save_pdf', and 'manipulate_pdf' indicates content modification. The description is empty, limiting direct evidence.
Attacks that exploit this kind of access
add_pdf_content. It is categorised as a Write tool in the oxidize-pdf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the oxidize-pdf MCP Server MCP server in PolicyLayer and add a rule for add_pdf_content: 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 oxidize-pdf MCP Server. Nothing to install.
add_pdf_content 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 add_pdf_content 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 add_pdf_content. 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.
add_pdf_content is provided by the oxidize-pdf MCP Server MCP server (bzsanti/oxidize-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
add_pdf_content is one line of oxidize-pdf MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →