publish_flow
Publish (activate) a draft flow or subflow. [Write]
This record as markdown: /tools/tedorigawa001-servicenow-mcp/publish-flow.md
What publish_flow does on ServiceNow-MCP
AI agents use publish_flow to create or update resources in ServiceNow-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Why publish_flow is rated Medium
Publishing a flow transitions it from an inactive draft state to an active, executable state. This is a reversible modification operation (flows can be unpublished or edited). While it affects business processes, it does not delete data or directly execute arbitrary external commands—it activates a pre-defined workflow.
From the tool's definition Tool name 'publish_flow' and description 'Publish (activate) a draft flow or subflow' indicates creation/modification of active workflows. The **[Write]** tag in the description explicitly confirms this classification.
Attacks that exploit this kind of access
The rule that runs publish_flow 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 publish_flow, this is the rule to start with:
publish_flow stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 publish_flow call is checked against it from then on.
Questions about publish_flow
Publish (activate) a draft flow or subflow. [Write]. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow MCP server in PolicyLayer and add a rule for publish_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.
publish_flow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the publish_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.
Set action: deny in the PolicyLayer policy for publish_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.
publish_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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue