get_subflow

What get_subflow does on ServiceNow-MCP

AI agents call get_subflow 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 get_subflow is rated Low

This tool retrieves metadata and configuration details about a ServiceNow subflow (inputs, outputs, actions). The verb 'Get' and absence of any modification language ('create', 'delete', 'execute', 'run') confirm this is a read-only operation. Blast radius is minimal—an AI agent querying subflow definitions cannot cause harm beyond accessing workflow metadata that likely has standard ServiceNow access controls.

From the tool's definition Tool name 'get_subflow' and description 'Get full details of a subflow including its inputs, outputs, and actions' indicate data retrieval with no modification or side effects.

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

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

Questions about get_subflow