AI agents invoke generate_pdf to trigger actions in Unphurl. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
audit_json | object | Yes | The complete audit JSON object produced during the audit pipeline. |
reseller_name | string | Yes | Your full name. |
reseller_email | string | Yes | Your contact email. |
reseller_position | string | — | Your position or title (optional). |
reseller_company_url | string | — | Your company URL (optional). |
Parameters from the server's own tool schema.
This tool executes a document generation process (rendering a PDF from provided data) and produces an external artifact with a time-limited download link. It triggers an external operation whose output depends on the arguments passed (audit JSON and reseller details). It is not a simple read/query, nor does it delete data or move money, so Execute is the most appropriate category.
From the tool's definition Generate a branded PDF audit report... Returns a 24-hour download link
Attacks that exploit this kind of access
Generate a branded PDF audit report. Pass the complete audit JSON object and your reseller details. Returns a 24-hour download link. It is categorised as a Execute tool in the Unphurl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
generate_pdf accepts 5 parameters: audit_json, reseller_name, reseller_email, reseller_position, reseller_company_url. Required: audit_json, reseller_name, reseller_email. The full parameter table on this page comes from the server's own tool schema.
Register the Unphurl MCP server in PolicyLayer and add a rule for generate_pdf: 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 Unphurl. Nothing to install.
generate_pdf 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 generate_pdf 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 generate_pdf. 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.
generate_pdf is provided by the Unphurl MCP server (123Ergo/unphurl-mcp). 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 →