render_graph · ContextForge MCP Gateway MCP: Risk & Policy

WHAT IT DOES

What render_graph does on ContextForge MCP Gateway

AI agents invoke render_graph to trigger actions in ContextForge MCP 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.

WHY IT NEEDS A POLICY

Why render_graph needs a policy

Rendering a DOT graph involves executing an external process or library (e.g., Graphviz) to transform input into an image. This is an execution action with side effects (file/image creation), not a simple read. Misuse could involve crafting malicious DOT content that exploits parser vulnerabilities, giving it medium severity.

From the tool's definition 'Render a DOT graph to an image' — the tool executes a rendering process (typically invoking Graphviz or similar engine) against a DOT-format input to produce output

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_graph Rate-limited

render_graph 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_graph": {
      "limits": [
        {
          "counter": "render_graph_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 ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about render_graph

What does the render_graph tool do? +

Render a DOT graph to an image. It is categorised as a Execute tool in the ContextForge MCP Gateway 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_graph? +

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

What risk level is render_graph? +

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

Can I rate-limit render_graph? +

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

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

render_graph is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.