generate_source_diagrams · Vaults Diagram Tools MCP

WHAT IT DOES

What generate_source_diagrams does on Vaults Diagram Tools

AI agents invoke generate_source_diagrams to trigger actions in Vaults Diagram Tools. 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 generate_source_diagrams needs a policy

This tool takes source code as input, processes it to generate diagrams, and renders image assets (SVG/JPEG). This constitutes executing a multi-step operation (code analysis + rendering) with side effects (file creation). It goes beyond a simple read/query and involves triggering external operations whose effects depend on the input source code.

From the tool's definition "Generate Mermaid diagrams from source code and render SVG/JPEG assets" — the tool processes/parses source code and executes a rendering pipeline to produce output assets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_source_diagrams Rate-limited

generate_source_diagrams 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": {
    "generate_source_diagrams": {
      "limits": [
        {
          "counter": "generate_source_diagrams_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 Vaults Diagram Tools, so you can run agents against it safely.

FAQ

Questions about generate_source_diagrams

What does the generate_source_diagrams tool do? +

Generate Mermaid diagrams from source code and render SVG/JPEG assets. It is categorised as a Execute tool in the Vaults Diagram Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_source_diagrams? +

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

What risk level is generate_source_diagrams? +

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

Can I rate-limit generate_source_diagrams? +

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

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

generate_source_diagrams is provided by the Vaults Diagram Tools MCP server (vaults-diagram-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.