render_artifact

Use this when the user asks to make or create a branded report, invoice, summary, release notes, or document — or to 'turn this Markdown/HTML into a PDF and PNG' (optionally with a logo or accent color). Do NOT use to screenshot an existing URL (use rendex_screenshot). Turns Markdown or HTML into...

Server Rendex Screenshot copperline-labs/rendex-mcp
Category Execute
Risk class High
Parameters 111 required

What render_artifact does on Rendex Screenshot

AI agents invoke render_artifact to trigger actions in Rendex Screenshot. 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.

ParameterTypeRequiredDescription
data object Optional Mustache data. When present, content is rendered as a logic-less Mustache template (plus the branding fields as {{logo}}/{{header}}/...) before convers
font string CSS font-family stack for the body (e.g. 'Georgia, serif').
logo string Absolute http(s) URL of a logo image shown in the header.
footer string Plain-text footer line shown at the bottom.
header string Plain-text header line shown beside the logo.
content string Yes The Markdown or HTML body to render (up to ~4MB).
formats array Which formats to produce. Each costs 1 credit. Default both.
expiresIn integer Seconds until the hosted URLs expire (3600-2592000). Default 86400 (24h).
pageSetup object Optional paper/viewport setup.
accentColor string CSS accent color for the bar, links, and headings (e.g. '#EA580C').
inputFormat string How to interpret content. 'markdown' is converted to styled HTML; 'html' is used as a body fragment.

Parameters from the server's own tool schema.

Why render_artifact needs a policy

This tool triggers an external rendering operation that produces and hosts files (PDF, PNG, share page), consuming render credits in the process. It is not a simple read or write — it executes an external pipeline that generates and publishes artifacts.

From the tool's definition Turns Markdown or HTML into a branded, downloadable artifact — a PDF, a PNG, and a hosted share page — in one call. Returns hosted URLs { pdfUrl, pngUrl, shareUrl, expiresAt }. Each requested format costs 1 render credit.

Risk signalsAccepts raw HTML/template content (content) · High parameter count (22 properties)

Questions about render_artifact

What does the render_artifact tool do? +

Use this when the user asks to make or create a branded report, invoice, summary, release notes, or document — or to 'turn this Markdown/HTML into a PDF and PNG' (optionally with a logo or accent color). Do NOT use to screenshot an existing URL (use rendex_screenshot). Turns Markdown or HTML into a branded, downloadable artifact — a PDF, a PNG, and a hosted share page — in one call. Apply a logo, accentColor, font, header, and footer. Returns hosted URLs { pdfUrl, pngUrl, shareUrl, expiresAt }. Each requested format costs 1 render credit. It is categorised as a Execute tool in the Rendex Screenshot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does render_artifact accept? +

render_artifact accepts 11 parameters: data, font, logo, footer, header, content, formats, expiresIn, pageSetup, accentColor, inputFormat. Required: content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on render_artifact? +

Register the Rendex Screenshot MCP server in PolicyLayer and add a rule for render_artifact: 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 Rendex Screenshot. Nothing to install.

What risk level is render_artifact? +

render_artifact is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit render_artifact? +

Yes. Add a rate_limit block to the render_artifact 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.

How do I block render_artifact completely? +

Set action: deny in the PolicyLayer policy for render_artifact. 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.

What MCP server provides render_artifact? +

render_artifact is provided by the Rendex Screenshot MCP server (copperline-labs/rendex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.