get_flow_node

Get a specific node in a 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/get-flow-node.md

WHAT IT DOES

What get_flow_node does on instantKOM MCP Server

AI agents call get_flow_node 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 get_flow_node is rated Low

The tool retrieves information about a specific node within a flow without creating, modifying, or deleting any data. This is a read-only query operation with minimal security risk—it exposes flow structure information but does not enable misuse with harmful side effects. The context of sibling tools (which include destructive operations like bulk_delete_custom_fields) confirms this is in the Read category.

From the tool's definition Tool name 'get_flow_node' and description 'Get a specific node in a flow' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_flow_node Allowed

get_flow_node 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": {
    "get_flow_node": {}
  }
}

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 get_flow_node call is checked against it from then on.

FAQ

Questions about get_flow_node

What does the get_flow_node tool do? +

Get a specific node in a 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 get_flow_node? +

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

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

Can I rate-limit get_flow_node? +

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

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

get_flow_node 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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