list_flows
List Flow Designer flows with optional filter by name, category, or active status
This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-flows.md
What list_flows does on ServiceNow-MCP
AI agents call list_flows to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_flows is rated Low
This is a pure query/read operation that retrieves information about Flow Designer flows without creating, modifying, deleting, or executing them. The use of 'list' and 'filter' indicates passive data retrieval. The blast radius of misuse is minimal as it only exposes metadata about existing flows without triggering actions or changing system state.
From the tool's definition Tool description states 'List Flow Designer flows with optional filter by name, category, or active status' - this is a retrieval operation with no modification, deletion, or execution of flows, only listing and filtering existing flows.
Attacks that exploit this kind of access
The rule that runs list_flows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_flows, this is the rule to start with:
list_flows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every list_flows call is checked against it from then on.
Questions about list_flows
List Flow Designer flows with optional filter by name, category, or active status. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP server in PolicyLayer and add a rule for list_flows: 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 ServiceNow-MCP. Nothing to install.
list_flows 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 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. 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 is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue