AI agents use prepare_signing_packet to create or update resources in PDF Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PDF Tools environment.
The tool fills form fields and appears to prepare documents for signing, which are reversible write operations. While it modifies PDF data, these changes can be undone by creating a new version of the document.
From the tool's definition Tool name 'prepare_signing_packet' combined with description 'One-shot workflow: fill form fields AND add' (appears truncated but indicates form field modification) and sibling tools 'create_signature' and 'add_signature_field' suggest the tool modifies PDF…
Documented attack patterns abuse exactly the kind of access prepare_signing_packet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for prepare_signing_packet:
{
"version": "1",
"default": "deny",
"tools": {
"prepare_signing_packet": {
"limits": [
{
"counter": "prepare_signing_packet_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}prepare_signing_packet 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.
One-shot workflow: fill form fields AND add. It is categorised as a Write tool in the PDF Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PDF Tools MCP server in PolicyLayer and add a rule for prepare_signing_packet: 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 Tools. Nothing to install.
prepare_signing_packet 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 prepare_signing_packet 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 prepare_signing_packet. 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.
prepare_signing_packet is provided by the PDF Tools MCP server (open-document-alliance/pdf-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 PDF Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 PDF Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.