Copy an existing ServiceNow Flow Designer flow into a target scoped application.
AI agents use copy_flow to create or update resources in Now Sdk Ext — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Now Sdk Ext environment.
The tool creates/duplicates data (a flow) rather than merely reading it, placing it in the Write category. Severity is medium because while flow duplication can impact system configuration and potentially affect automated processes, it is reversible (the copied flow can be deleted) and does not involve financial transactions, destructive operations, or arbitrary code execution.
From the tool's definition Tool description states 'Copy an existing ServiceNow Flow Designer flow into a target scoped application' — this creates a new copy of a flow, which is a reversible write operation that modifies the state of the ServiceNow instance by adding new objects.
Documented attack patterns abuse exactly the kind of access copy_flow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Now Sdk Ext, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_flow:
{
"version": "1",
"default": "deny",
"tools": {
"copy_flow": {
"limits": [
{
"counter": "copy_flow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}copy_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.
Free to start. No card required.
Copy an existing ServiceNow Flow Designer flow into a target scoped application. It is categorised as a Write tool in the Now Sdk Ext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Now Sdk Ext MCP server in PolicyLayer and add a rule for copy_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 Now Sdk Ext. Nothing to install.
copy_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 copy_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 copy_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.
copy_flow is provided by the Now Sdk Ext MCP server (sonisoft-cnanda/now-sdk-ext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Now Sdk Ext, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
86 Now Sdk Ext tools catalogued and risk-classified — across an index of 43,000+ MCP servers.