markdown_to_html
Markdown to HTML Converter — Convert a bounded Markdown subset (headings, bold/italic, links, lists, code) to HTML, with all literal text HTML-escaped.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/markdown-to-html.md
What markdown_to_html does on Gateway
AI agents invoke markdown_to_html to trigger actions in Gateway. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
markdown | string | Yes | Markdown source to convert |
Parameters from the server's own tool schema.
Why markdown_to_html is rated High
The tool performs a transformation/computation (converting Markdown to HTML), which is closer to Execute (runs a conversion process) than Read or Write. It has no persistent side effects, no data storage, and no destructive capability. Severity is low because the operation is bounded, sandboxed to a Markdown subset, and HTML-escaped, limiting injection risk.
From the tool's definition 'Convert a bounded Markdown subset... to HTML' — transforms input content and produces output HTML
Attacks that exploit this kind of access
The rule that runs markdown_to_html safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For markdown_to_html, this is the rule to start with:
markdown_to_html stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every markdown_to_html call is checked against it from then on.
Questions about markdown_to_html
Markdown to HTML Converter — Convert a bounded Markdown subset (headings, bold/italic, links, lists, code) to HTML, with all literal text HTML-escaped. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
markdown_to_html accepts 1 parameter: markdown. Required: markdown. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for markdown_to_html: 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 Gateway. Nothing to install.
markdown_to_html is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the markdown_to_html 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 markdown_to_html. 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.
markdown_to_html is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue