lint
Check emailmd markdown for deliverability, accessibility, and readability problems without rendering it: missing alt text, http:// links, Gmail's 102KB clip limit, generic link text, spam-trigger phrases, and more. Fix warnings before sending; suggestions are sometimes intentional (e.g. transacti...
This record as markdown: /tools/dev-emailmd-emailmd/lint.md
What lint does on Emailmd
AI agents call lint 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 |
|---|---|---|---|
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 lint is rated Low
Lint analyzes content for issues only; no data modification or external effects.
From the tool's definition Check emailmd markdown...without rendering it
Attacks that exploit this kind of access
The rule that runs lint 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 lint, this is the rule to start with:
lint 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 lint call is checked against it from then on.
Questions about lint
Check emailmd markdown for deliverability, accessibility, and readability problems without rendering it: missing alt text, http:// links, Gmail's 102KB clip limit, generic link text, spam-trigger phrases, and more. Fix warnings before sending; suggestions are sometimes intentional (e.g. transactional emails without an unsubscribe link). It is categorised as a Read tool in the Emailmd MCP Server, which means it retrieves data without modifying state.
lint accepts 2 parameters: 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 lint: 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.
lint 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 lint 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 lint. 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.
lint 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