render_auto_diagram · Vizdown- MCP: Risk & Policy

WHAT IT DOES

What render_auto_diagram does on Vizdown-MCP

AI agents invoke render_auto_diagram to trigger actions in Vizdown-MCP. 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_auto_diagram needs a policy

Based on the server context, this tool likely renders diagrams automatically (possibly detecting diagram type), similar to sibling tools like render_diagram and render_all_diagrams. Rendering involves executing Mermaid.js or SVG renderers to produce output files, which classifies as Execute. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'render_auto_diagram'; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_auto_diagram Rate-limited

render_auto_diagram 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_auto_diagram": {
      "limits": [
        {
          "counter": "render_auto_diagram_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 Vizdown-MCP, so you can run agents against it safely.

FAQ

Questions about render_auto_diagram

What does the render_auto_diagram tool do? +

render_auto_diagram. It is categorised as a Execute tool in the Vizdown-MCP 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_auto_diagram? +

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

What risk level is render_auto_diagram? +

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

Can I rate-limit render_auto_diagram? +

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

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

render_auto_diagram is provided by the Vizdown- MCP server (rutika196/clarity-beta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.