Add edges in the knowledge graph, connecting two nodes to build a relationship network. Edges represent relationship types between nodes, such as dependencies, containment, associations, etc. Prerequisites: 1. Must first create a graph (using create_graph) 2. Source and target nodes must already ...
Part of the Knowledge Graph Server server.
Free to start. No card required.
AI agents use add_edge to create or modify resources in Knowledge Graph Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call add_edge repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Knowledge Graph Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"add_edge": {
"limits": [
{
"counter": "add_edge_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Knowledge Graph Server policy for all 15 tools.
These attack patterns abuse exactly the kind of access add_edge gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Add edges in the knowledge graph, connecting two nodes to build a relationship network. Edges represent relationship types between nodes, such as dependencies, containment, associations, etc. Prerequisites: 1. Must first create a graph (using create_graph) 2. Source and target nodes must already exist 3. Edge type must match the graph type Usage recommendations: 1. First use list_graphs to get graph and node information 2. Confirm both source and target nodes exist and their types match 3. Choose appropriate edge type based on graph type 4. Add meaningful labels to edges to help understand relationships 5. If relationships have varying strengths, use the weight parameter Return data: - data: Newly created edge information * id: Edge ID * type: Edge type * sourceId: Source node ID * targetId: Target node ID * label: Edge label * weight: Edge weight. It is categorised as a Write tool in the Knowledge Graph Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge Graph Server 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 Knowledge Graph Server. 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 Knowledge Graph Server MCP server (aiuluna/knowledge-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Knowledge Graph Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.