get_subflow
Get full details of a subflow including its inputs, outputs, and actions
This record as markdown: /tools/servicenow-mcp-server/get-subflow.md
What get_subflow does on ServiceNow MCP Server
AI agents call get_subflow 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 get_subflow is rated Low
This tool retrieves metadata about a ServiceNow subflow (inputs, outputs, actions). It performs a read-only query operation with no side effects, no code execution, no data modification, and no irreversible actions. The retrieval of workflow definitions poses minimal risk as it is informational only.
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 execution.
Attacks that exploit this kind of access
The rule that runs get_subflow 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 get_subflow, this is the rule to start with:
get_subflow 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 get_subflow call is checked against it from then on.
Questions about get_subflow
Get full details of a subflow including its inputs, outputs, and actions. 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 get_subflow: 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.
get_subflow 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 get_subflow 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 get_subflow. 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.
get_subflow 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