Fill a named PDF template's AcroForm fields and write to output_path.
AI agents use create_pdf_from_template to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
This tool creates or modifies a PDF file by populating template fields and writing it to disk. This is a reversible Write operation—the output can be edited, deleted, or overwritten. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states "Fill a named PDF template's AcroForm fields and write to output_path." The verb 'write' and the action of filling form fields and saving output indicate data creation/modification.
Attacks that exploit this kind of access
Fill a named PDF template's AcroForm fields and write to output_path. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core MCP server in PolicyLayer and add a rule for create_pdf_from_template: 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 Nexus Core. Nothing to install.
create_pdf_from_template 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 create_pdf_from_template 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 create_pdf_from_template. 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.
create_pdf_from_template is provided by the Nexus Core MCP server (noumenon-ai/nexus-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →