Export project artifacts as a professional, print-ready HTML document. Converts one or more markdown files into styled HTML with a cover page, section headers, and @media print rules. Users open the HTML in a browser and use Cmd+P / Ctrl+P to save as PDF. Supports any markdown file in the project...
AI agents use pdf_export to create or update resources in RC Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RC Engine environment.
This tool generates and writes new HTML files to the filesystem based on input markdown. It is a reversible, non-destructive write operation—the original markdown files remain unchanged, the created HTML files can be deleted, and the operation has no side effects beyond file creation. It does not read sensitive data beyond what users explicitly provide, execute arbitrary code, delete anything, or move money.
From the tool's definition Tool description states it 'converts' markdown files into styled HTML and 'saves the HTML' to a directory (rc-method/exports/), creating new files as output.
Attacks that exploit this kind of access
Export project artifacts as a professional, print-ready HTML document. Converts one or more markdown files into styled HTML with a cover page, section headers, and @media print rules. Users open the HTML in a browser and use Cmd+P / Ctrl+P to save as PDF. Supports any markdown file in the project (PRDs, playbook, design briefs, reports). Saves the HTML to rc-method/exports/. It is categorised as a Write tool in the RC Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RC Engine MCP server in PolicyLayer and add a rule for pdf_export: 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 RC Engine. Nothing to install.
pdf_export 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 pdf_export 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 pdf_export. 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.
pdf_export is provided by the RC Engine MCP server (originalrashmi/rc-engine-product-framework). 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 →