render_markup

Render markup text to HTML

SERVERForgejo SOURCEsqcows/forgejo-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/render-markup.md

WHAT IT DOES

What render_markup does on Forgejo

AI agents invoke render_markup 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.

RISK

Why render_markup is rated High

Rendering markup to HTML involves executing a server-side transformation process. While it doesn't modify stored data or delete anything, it triggers an external operation (server-side rendering) whose output depends on the input arguments. It could potentially be misused to probe server-side rendering behavior or trigger server-side processing of malicious markup.

From the tool's definition "Render markup text to HTML" — this tool processes/executes a transformation of input content

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs render_markup 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_markup, this is the rule to start with:

render_markup Rate-limited

render_markup 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "render_markup": {
      "limits": [
        {
          "counter": "render_markup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every render_markup call is checked against it from then on.

FAQ

Questions about render_markup

What does the render_markup tool do? +

Render markup 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.

How do I enforce a policy on render_markup? +

Register the Forgejo MCP server in PolicyLayer and add a rule for render_markup: 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.

What risk level is render_markup? +

render_markup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit render_markup? +

Yes. Add a rate_limit block to the render_markup 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.

How do I block render_markup completely? +

Set action: deny in the PolicyLayer policy for render_markup. 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.

What MCP server provides render_markup? +

render_markup 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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →