Publish (activate) a draft flow or subflow. [Write]
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.
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
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →