update_catalog_category · ServiceNow MCP Server MCP

WHAT IT DOES

What update_catalog_category does on ServiceNow MCP Server

AI agents use update_catalog_category to create or update resources in ServiceNow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.

WHY IT NEEDS A POLICY

Why update_catalog_category needs a policy

This tool modifies existing catalog category records in ServiceNow, which is a Write operation. It creates or alters data reversibly without deletion or execution of arbitrary code. Severity is medium because incorrect updates could affect service catalog availability or user navigation, but changes are typically reversible through subsequent updates.

From the tool's definition Tool name 'update_catalog_category' and description 'Update an existing service catalog category in ServiceNow' indicate modification of catalog configuration data. Updates are reversible changes to metadata/configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_catalog_category Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_catalog_category": {
      "limits": [
        {
          "counter": "update_catalog_category_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow MCP Server, so you can run agents against it safely.

FAQ

Questions about update_catalog_category

What does the update_catalog_category tool do? +

Update an existing service catalog category in ServiceNow. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_catalog_category? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for update_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 ServiceNow MCP Server. Nothing to install.

What risk level is update_catalog_category? +

update_catalog_category is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_catalog_category? +

Yes. Add a rate_limit block to the update_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.

How do I block update_catalog_category completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_catalog_category? +

update_catalog_category is provided by the ServiceNow MCP Server MCP server (shameerampcome/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.