# 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).

Agent View of the PolicyLayer registry record for `render`. HTML page: https://policylayer.com/tools/dev-emailmd-emailmd/render

## Facts

- Tool: `render`
- Server: Emailmd (`emailmd`) — https://policylayer.com/tools/dev-emailmd-emailmd.md
- Install: `npx -y emailmd`
- Homepage: https://github.com/anypost/emailmd
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `minify` | boolean | no | 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 | no | Named markdown partials spliced in wherever the document says "::: include <name>". |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "render",
    "arguments": {
      "markdown": "<markdown>"
    }
  }
}
```

## Why render is rated Low

Tool converts markdown to HTML with no side effects or external modifications.

From the tool's own definition: "Render markdown into email-safe HTML, returns html, text, meta"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Emailmd:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "render": {}
  }
}
```

## Other tools on Emailmd (2)

- `lint` — Read — https://policylayer.com/tools/dev-emailmd-emailmd/lint.md
- `read_docs` — Read — https://policylayer.com/tools/dev-emailmd-emailmd/read-docs.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-emailmd-emailmd · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-emailmd-emailmd