kg_create_edge
Create a typed relationship (edge) between two entities in the knowledge graph. Common edge types: uses, depends_on, part_of, created_by, maintained_by, deployed_to, connects_to, extends, implements, references, owns, belongs_to, related_to, blocked_by, replaced_by.
This record as markdown: /tools/cowork-os/kg-create-edge.md
What kg_create_edge does on CoWork OS
AI agents use kg_create_edge to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why kg_create_edge is rated Medium
This is a Write operation because it creates new data (edges/relationships) in the knowledge graph in a reversible manner. While it modifies the graph structure, the operation is not destructive—relationships can be removed or updated later.
From the tool's definition Tool creates a typed relationship (edge) between entities in a knowledge graph. The description explicitly states 'Create' and lists relationship types like 'uses', 'depends_on', 'part_of', etc., which are additive, reversible modifications to graph structure.
Attacks that exploit this kind of access
The rule that runs kg_create_edge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kg_create_edge, this is the rule to start with:
kg_create_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 CoWork OS, apply this rule, and every kg_create_edge call is checked against it from then on.
Questions about kg_create_edge
Create a typed relationship (edge) between two entities in the knowledge graph. Common edge types: uses, depends_on, part_of, created_by, maintained_by, deployed_to, connects_to, extends, implements, references, owns, belongs_to, related_to, blocked_by, replaced_by. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for kg_create_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 CoWork OS. Nothing to install.
kg_create_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 kg_create_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 kg_create_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.
kg_create_edge is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue