render
Render emailmd markdown into email-safe HTML. Returns html (the complete email document), text (the plain-text MIME part), meta (frontmatter), warnings (non-fatal repairs made while rendering; aim for none), htmlBytes, and previewUrl (a live browser preview of this exact document to share with th...
This record as markdown: /tools/dev-emailmd-emailmd/render.md
What render does on Emailmd
AI agents call render to retrieve information from Emailmd without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
minify | boolean | — | Minify the HTML. Recommended for sending; helps stay under Gmail's 102KB clip limit. |
markdown | string | Yes | The emailmd markdown document, optionally starting with YAML frontmatter. |
partials | object | — | Named markdown partials spliced in wherever the document says "::: include <name>". |
Parameters from the server's own tool schema.
Why render is rated Low
Tool converts markdown to HTML with no side effects or external modifications.
From the tool's definition Render markdown into email-safe HTML, returns html, text, meta
Attacks that exploit this kind of access
The rule that runs render safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Emailmd, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render, this is the rule to start with:
render is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Emailmd, apply this rule, and every render call is checked against it from then on.
Questions about render
Render emailmd markdown into email-safe HTML. Returns html (the complete email document), text (the plain-text MIME part), meta (frontmatter), warnings (non-fatal repairs made while rendering; aim for none), htmlBytes, and previewUrl (a live browser preview of this exact document to share with the user). It is categorised as a Read tool in the Emailmd MCP Server, which means it retrieves data without modifying state.
render accepts 3 parameters: minify, markdown, partials. Required: markdown. The full parameter table on this page comes from the server's own tool schema.
Register the Emailmd MCP server in PolicyLayer and add a rule for render: 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 Emailmd. Nothing to install.
render is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the render 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 render. 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.
render is provided by the Emailmd MCP server (emailmd). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Emailmd, and thousands of servers like it.
This server
Across the catalogue