Moves one or more service catalog items to a new category.
AI agents use move_catalog_items to create or update resources in Snow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Snow environment.
This tool modifies the organizational structure of service catalog items by changing their category assignments. This is a reversible write operation—the items and their data remain intact, but their metadata/categorization is altered. It does not delete data (Destructive), execute external code (Execute), involve financial transactions (Financial), or merely read data (Read).
From the tool's definition The tool description states it 'Moves one or more service catalog items to a new category,' which is a modification operation that reorganizes data within ServiceNow's service catalog.
Documented attack patterns abuse exactly the kind of access move_catalog_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for move_catalog_items:
{
"version": "1",
"default": "deny",
"tools": {
"move_catalog_items": {
"limits": [
{
"counter": "move_catalog_items_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_catalog_items 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.
Moves one or more service catalog items to a new category. It is categorised as a Write tool in the Snow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Snow MCP server in PolicyLayer and add a rule for move_catalog_items: 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 Snow. Nothing to install.
move_catalog_items 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 move_catalog_items 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 move_catalog_items. 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.
move_catalog_items is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, 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.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.