List all nodes in a specific flow
AI agents call get_flow_nodes to retrieve information from Spiderchat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves structural information about a flow without creating, modifying, deleting, or executing any operations. It is a straightforward read operation consistent with the sibling tools (list_flows_in_group, search_facts, etc.) which are all Read category. The blast radius is minimal as it only exposes existing data.
From the tool's definition Tool name is 'get_flow_nodes' and description states 'List all nodes in a specific flow' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all nodes in a specific flow. It is categorised as a Read tool in the Spiderchat MCP Server, which means it retrieves data without modifying state.
Register the Spiderchat MCP server in PolicyLayer and add a rule for get_flow_nodes: 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 Spiderchat. Nothing to install.
get_flow_nodes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_flow_nodes 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 get_flow_nodes. 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.
get_flow_nodes is provided by the Spiderchat MCP server (spider-chat/spiderchat-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →