create_flow_edge
Create a connection between two nodes in a flow. Both nodes must exist in the same flow.
This record as markdown: /tools/instantkom-mcp-server/create-flow-edge.md
What create_flow_edge does on instantKOM MCP Server
AI agents use create_flow_edge to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.
Why create_flow_edge is rated Medium
This tool adds or creates a new relationship between flow nodes. This is a data modification operation that is reversible (edges can be removed or modified later). While it could be part of a larger workflow system, the tool itself only creates structural connections within a flow definition and does not execute external operations, delete data, or involve financial transactions.
From the tool's definition Tool creates a connection between nodes in a flow, which is a reversible modification operation (not a read, not destructive, not execution of external code, not financial). The action 'create' modifies flow structure by adding a new edge relationship.
Attacks that exploit this kind of access
The rule that runs create_flow_edge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_flow_edge, this is the rule to start with:
create_flow_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 instantKOM MCP Server, apply this rule, and every create_flow_edge call is checked against it from then on.
Questions about create_flow_edge
Create a connection between two nodes in a flow. Both nodes must exist in the same flow. It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for create_flow_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 instantKOM MCP Server. Nothing to install.
create_flow_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 create_flow_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 create_flow_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.
create_flow_edge is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue