test_flow · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What test_flow does on ServiceNow-MCP

AI agents invoke test_flow to trigger actions in ServiceNow-MCP. 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.

WHY IT NEEDS A POLICY

Why test_flow needs a policy

Despite being labeled '[Write]' by the server, executing a flow constitutes running external operations whose effects depend on the flow's content and arguments. Test mode may still trigger side effects (notifications, record updates, integrations). The most severe applicable category is Execute, not Write. Severity is high because flows in ServiceNow can orchestrate complex multi-system operations.

From the tool's definition 'Execute a flow in test mode with sample inputs' — the tool actively runs/executes a flow, even if in test mode, triggering real operations depending on flow logic

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow-MCP, so you can run agents against it safely.

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 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 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. 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 (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.