add_edge
Add an edge to a DOT graph
This record as markdown: /tools/jrmatherly-mcp-context-forge/add-edge.md
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 add_edge is rated Medium
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
The rule that runs add_edge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_edge, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every add_edge call is checked against it from then on.
Questions about add_edge
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.
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.
add_edge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue