List all flows in a specific group, optionally including nested subgroups
AI agents call list_flows_in_group 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 retrieves and lists existing flow objects within a group hierarchy. It is a read-only query operation that returns information without creating, modifying, deleting, or executing any actions. The optional inclusion of nested subgroups does not change its fundamental nature as a data retrieval operation.
From the tool's definition Tool name is 'list_flows_in_group' and description states 'List all flows in a specific group' — a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
List all flows in a specific group, optionally including nested subgroups. 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 list_flows_in_group: 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.
list_flows_in_group 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 list_flows_in_group 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 list_flows_in_group. 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.
list_flows_in_group 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 →