AI agents use fill_with_profile 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 creates or modifies data (PDF form fields) in a reversible manner. Filling PDF fields is a modification operation but not destructive—the changes can be undone or overwritten. It does not delete data, execute arbitrary code, or move money, placing it squarely in Write.
From the tool's definition Tool name 'fill_with_profile' and description 'Fill a PDF using a saved profile' indicate the tool modifies PDF content by populating fields. The server description confirms these are PDF workflow tools that 'fill' PDFs.
Documented attack patterns abuse exactly the kind of access fill_with_profile 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 fill_with_profile:
{
"version": "1",
"default": "deny",
"tools": {
"fill_with_profile": {
"limits": [
{
"counter": "fill_with_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fill_with_profile 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.
Fill a PDF using a saved profile. 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 fill_with_profile: 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.
fill_with_profile 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 fill_with_profile 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 fill_with_profile. 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.
fill_with_profile 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.