add_edge · ContextForge MCP Gateway MCP: Risk & Policy

WHAT IT DOES

What add_edge does on ContextForge MCP Gateway

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

WHY IT NEEDS A POLICY

Why add_edge needs a policy

The tool adds an edge (a connection between two nodes) to a DOT graph data structure. This is a creation operation that modifies the graph reversibly—edges can be removed or modified later. It does not execute code, delete data irreversibly, move money, or trigger external side effects. The blast radius is limited to the graph structure being modified. Classified as Write with low severity.

From the tool's definition Tool name and description: 'Add an edge to a DOT graph' - creates/modifies graph structure by adding an edge, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_edge Rate-limited

add_edge 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_edge": {
      "limits": [
        {
          "counter": "add_edge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 add_edge

What does the add_edge tool do? +

Add an edge to a DOT graph. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_edge? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for add_edge: 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 add_edge? +

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

Can I rate-limit add_edge? +

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

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

add_edge 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.