create_flow_action
Create a custom Flow Designer action. [Scripting]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/create-flow-action.md
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 create_flow_action is rated High
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
The rule that runs create_flow_action 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 create_flow_action, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every create_flow_action call is checked against it from then on.
Questions about create_flow_action
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.
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.
create_flow_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on ServiceNow, and thousands of servers like it.
Across the catalogue