AI agents use update_pdf_metadata to create or update resources in PDF MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF MCP Server environment.
Updating metadata modifies PDF properties reversibly without deleting data or executing arbitrary code. This falls under Write category. Severity is medium because metadata modifications could alter document provenance, timestamps, or embedded information in ways that affect integrity or compliance, but the operation is reversible and does not destroy data or execute commands.
From the tool's definition Tool name 'update_pdf_metadata' indicates modification of PDF metadata fields. Server description confirms the MCP enables 'PDF manipulation' operations including reversible modifications.
Documented attack patterns abuse exactly the kind of access update_pdf_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_pdf_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"update_pdf_metadata": {
"limits": [
{
"counter": "update_pdf_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_pdf_metadata 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.
update_pdf_metadata. It is categorised as a Write tool in the PDF MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF MCP Server MCP server in PolicyLayer and add a rule for update_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 MCP Server. Nothing to install.
update_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 update_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 update_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.
update_pdf_metadata is provided by the PDF MCP Server MCP server (sohaib-2/pdf-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PDF 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.
22 PDF MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.