test_flow

Execute a flow in test mode with sample inputs. [Write]

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/test-flow.md

WHAT IT DOES

What test_flow does on ServiceNow MCP Server

AI agents invoke test_flow to trigger actions in ServiceNow MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why test_flow is rated High

The tool executes a flow, which triggers external operations and runs logic within ServiceNow. Even in 'test mode', executing a flow can have real side effects depending on the flow's actions (e.g., sending notifications, modifying records). This makes it Execute rather than Write. The self-labeled '[Write]' tag in the description is overridden by the more severe Execute classification per the rules.

From the tool's definition "Execute a flow in test mode with sample inputs"

Attacks that exploit this kind of access

RECOMMENDED RULE

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

test_flow Rate-limited

test_flow stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_flow": {
      "limits": [
        {
          "counter": "test_flow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about test_flow

What does the test_flow tool do? +

Execute a flow in test mode with sample inputs. [Write]. It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_flow? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for test_flow: 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.

What risk level is test_flow? +

test_flow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_flow? +

Yes. Add a rate_limit block to the test_flow 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 test_flow completely? +

Set action: deny in the PolicyLayer policy for test_flow. 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 test_flow? +

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

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 365 ServiceNow MCP Server tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →