create_flow_action · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What create_flow_action does on ServiceNow-MCP

AI agents invoke create_flow_action 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 create_flow_action needs a policy

Creating a Flow Designer action involves defining executable logic/scripts that will run as part of automated workflows in ServiceNow. The [Scripting] tag confirms code execution capability is involved. While it is technically a 'create' (Write) operation, the artifact produced is executable workflow automation code, making Execute the most appropriate and severe category.

From the tool's definition 'Create a custom Flow Designer action' and '[Scripting]' tag indicate this tool creates executable workflow automation logic involving scripting

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_flow_action Rate-limited

create_flow_action 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": {
    "create_flow_action": {
      "limits": [
        {
          "counter": "create_flow_action_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 create_flow_action

What does the create_flow_action tool do? +

Create a custom Flow Designer action. [Scripting]. 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 create_flow_action? +

Register the ServiceNow- MCP server in PolicyLayer and add a rule for create_flow_action: 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 create_flow_action? +

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

Can I rate-limit create_flow_action? +

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

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

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