List Flow Designer flows with optional filter by name, category, or active status
AI agents call list_flows to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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 →