list_subflows

List available subflows that can be reused across flows

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-subflows.md

WHAT IT DOES

What list_subflows does on ServiceNow-MCP

AI agents call list_subflows 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.

RISK

Why list_subflows is rated Low

This tool retrieves or queries information about available subflows without creating, modifying, executing, or deleting any data. It is a straightforward informational lookup operation, consistent with the Read category. The low severity reflects minimal blast radius if misused—an agent could at most discover available subflows but not execute them or modify data.

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 modification or execution of flows.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_subflows 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_subflows, this is the rule to start with:

list_subflows Allowed

list_subflows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_subflows": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every list_subflows call is checked against it from then on.

FAQ

Questions about list_subflows

What does the list_subflows tool do? +

List available subflows that can be reused across flows. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_subflows? +

Register the ServiceNow 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. Nothing to install.

What risk level is list_subflows? +

list_subflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_subflows? +

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.

How do I block list_subflows completely? +

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.

What MCP server provides list_subflows? +

list_subflows 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.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →