list_subflows
List available subflows that can be reused across flows
This record as markdown: /tools/servicenow-mcp-server/list-subflows.md
What list_subflows does on ServiceNow MCP Server
AI agents call list_subflows to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_subflows is rated Low
This tool lists or retrieves metadata about available subflows for informational purposes. It performs a read-only query operation that does not create, modify, delete, or execute any workflows. The action of listing available reusable components poses minimal risk even if misused by an AI agent, as it only surfaces existing configuration information without triggering any business logic or state changes.
From the tool's definition Tool name 'list_subflows' and description 'List available subflows that can be reused across flows' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_subflows safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_subflows, this is the rule to start with:
list_subflows 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 Server, apply this rule, and every list_subflows call is checked against it from then on.
Questions about list_subflows
List available subflows that can be reused across flows. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for list_subflows: 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 Server. Nothing to install.
list_subflows 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_subflows 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_subflows. 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_subflows is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue