Creates a new category within a specified Service Catalog.
AI agents use create_catalog_category 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 creates new data (a catalog category) within ServiceNow's Service Catalog, which is a Write operation. While creation is reversible (categories can be deleted), misconfiguration could disrupt service catalog organization and affect end-user self-service capabilities.
From the tool's definition Tool name is 'create_catalog_category' and description states it 'Creates a new category within a specified Service Catalog', indicating irreversible data creation in a business-critical service catalog system.
Documented attack patterns abuse exactly the kind of access create_catalog_category 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 create_catalog_category:
{
"version": "1",
"default": "deny",
"tools": {
"create_catalog_category": {
"limits": [
{
"counter": "create_catalog_category_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_catalog_category 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.
Creates a new category within a specified Service Catalog. 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 create_catalog_category: 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.
create_catalog_category 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 create_catalog_category 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 create_catalog_category. 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.
create_catalog_category 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.