Clone an existing update set by creating a new one and copying all its records.
AI agents use clone_update_set 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 new data (cloning/copying an update set and its records) rather than reading, executing arbitrary code, or destroying data. While cloning is a write operation that modifies system state by adding new records, it is reversible (the cloned update set can be deleted).
From the tool's definition Clone an existing update set by creating a new one and copying all its records. This action creates new data (a new update set) and copies records, which are reversible write operations.
Documented attack patterns abuse exactly the kind of access clone_update_set 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 clone_update_set:
{
"version": "1",
"default": "deny",
"tools": {
"clone_update_set": {
"limits": [
{
"counter": "clone_update_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}clone_update_set 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.
Clone an existing update set by creating a new one and copying all its records. 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 clone_update_set: 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.
clone_update_set 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 clone_update_set 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 clone_update_set. 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.
clone_update_set 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.