render_diff_file · Markview MCP: Risk & Policy

WHAT IT DOES

What render_diff_file does on Markview

AI agents invoke render_diff_file to trigger actions in Markview. 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 IT NEEDS A POLICY

Why render_diff_file needs a policy

The tool executes a git diff command on a repository, which involves running an external process/shell operation. While it is primarily a read-like operation (viewing differences), it triggers an external command execution (git) and renders output through another tool (diff2html), placing it in the Execute category. Misuse could expose sensitive repository contents or be used to probe repository state.

From the tool's definition Run git diff on a repository and render the output in MarkView with diff2html

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_diff_file Rate-limited

render_diff_file 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_diff_file": {
      "limits": [
        {
          "counter": "render_diff_file_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Markview, so you can run agents against it safely.

FAQ

Questions about render_diff_file

What does the render_diff_file tool do? +

Run git diff on a repository and render the output in MarkView with diff2html. It is categorised as a Execute tool in the Markview 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_diff_file? +

Register the Markview MCP server in PolicyLayer and add a rule for render_diff_file: 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 Markview. Nothing to install.

What risk level is render_diff_file? +

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

Can I rate-limit render_diff_file? +

Yes. Add a rate_limit block to the render_diff_file 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_diff_file completely? +

Set action: deny in the PolicyLayer policy for render_diff_file. 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_diff_file? +

render_diff_file is provided by the Markview MCP server (mcp-server-markview). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.