This record as markdown: /tools/sqcows-forgejo-mcp/render-markdown.md
What render_markdown does on Forgejo
AI agents invoke render_markdown to trigger actions in Forgejo. 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.
Why render_markdown is rated High
This tool processes/transforms input by executing a rendering operation on the server side. While it doesn't modify stored data, it executes a transformation operation (markdown to HTML conversion) which may involve server-side processing and could potentially be used to probe server behavior or trigger rendering issues. It's more than a pure read, as it actively processes and transforms content.
From the tool's definition Render markdown text to HTML
Attacks that exploit this kind of access
The rule that runs render_markdown safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_markdown, this is the rule to start with:
render_markdown 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 Forgejo, apply this rule, and every render_markdown call is checked against it from then on.
Questions about render_markdown
Render markdown text to HTML. It is categorised as a Execute tool in the Forgejo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Forgejo MCP server in PolicyLayer and add a rule for render_markdown: 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 Forgejo. Nothing to install.
render_markdown 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 render_markdown 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_markdown. 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_markdown is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Forgejo, and thousands of servers like it.
Across the catalogue