New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_flow_action

Create a custom Flow Designer action. [Scripting]

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

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.

More on ServiceNow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceNow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.