Medium Risk

generate_diff_diagram

Generate a Mermaid diagram showing differences between two versions of code

How to control generate_diff_diagram ↓

AI agents use generate_diff_diagram to create or update resources in Archy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Archy environment.

Medium Risk

An AI agent can call generate_diff_diagram faster than any human can review — one bad instruction and it creates or modifies resources in Archy by the hundred, each call as confident as the last.

Documented attack patterns abuse exactly the kind of access generate_diff_diagram gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Archy, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_diff_diagram:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_diff_diagram": {
      "limits": [
        {
          "counter": "generate_diff_diagram_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

generate_diff_diagram stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Archy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the generate_diff_diagram tool do? +

Generate a Mermaid diagram showing differences between two versions of code. It is categorised as a Write tool in the Archy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_diff_diagram? +

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

What risk level is generate_diff_diagram? +

generate_diff_diagram is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_diff_diagram? +

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

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

generate_diff_diagram is provided by the Archy MCP server (phxdev1/archy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Archy tool call.

Deterministic rules across all 9 Archy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Archy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.