list_flow_edges

List all edges (connections between nodes) in a specific flow

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/list-flow-edges.md

WHAT IT DOES

What list_flow_edges does on instantKOM MCP Server

AI agents call list_flow_edges to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_flow_edges is rated Low

The tool retrieves and queries flow graph structure (edges/connections) without creating, modifying, deleting, or executing any operations. This is a pure data retrieval function with no side effects, placing it firmly in the Read category. Low severity due to limited blast radius—knowing flow structure is informational only.

From the tool's definition Tool name 'list_flow_edges' and description 'List all edges (connections between nodes) in a specific flow' indicate a read-only query operation that retrieves structural information about a flow without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_flow_edges 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 list_flow_edges, this is the rule to start with:

list_flow_edges Allowed

list_flow_edges is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_flow_edges": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every list_flow_edges call is checked against it from then on.

FAQ

Questions about list_flow_edges

What does the list_flow_edges tool do? +

List all edges (connections between nodes) in a specific flow. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_flow_edges? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for list_flow_edges: 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.

What risk level is list_flow_edges? +

list_flow_edges is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_flow_edges? +

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

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

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

KEEP EXPLORING

More on instantKOM MCP Server, and thousands of servers like it.

This server

All 245 instantKOM MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →