🔧 PDF Post-Processing Unified Tool - ⚠️ IMPORTANT: This is a necessary follow-up step for playwright-mcp\
AI agents invoke process_pdf_post_conversion to trigger actions in Doc Ops. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool appears to execute post-processing operations on PDFs, potentially involving external tooling (playwright-mcp), which indicates it runs operations beyond simple data retrieval or plain document creation. The playwright reference suggests browser-level execution. Severity is medium as it processes files but has limited blast radius beyond the document scope.
From the tool's definition 'PDF Post-Processing Unified Tool' and 'necessary follow-up step for playwright-mcp' — implies triggering external operations or browser automation via playwright
Documented attack patterns abuse exactly the kind of access process_pdf_post_conversion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for process_pdf_post_conversion:
{
"version": "1",
"default": "deny",
"tools": {
"process_pdf_post_conversion": {
"limits": [
{
"counter": "process_pdf_post_conversion_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}process_pdf_post_conversion stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
🔧 PDF Post-Processing Unified Tool - ⚠️ IMPORTANT: This is a necessary follow-up step for playwright-mcp\. It is categorised as a Execute tool in the Doc Ops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Doc Ops MCP server in PolicyLayer and add a rule for process_pdf_post_conversion: 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 Doc Ops. Nothing to install.
process_pdf_post_conversion is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the process_pdf_post_conversion 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 process_pdf_post_conversion. 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.
process_pdf_post_conversion is provided by the Doc Ops MCP server (tele-ai/doc-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Doc Ops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Doc Ops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.