create_catalog_ui_policy · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What create_catalog_ui_policy does on ServiceNow-MCP

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

WHY IT NEEDS A POLICY

Why create_catalog_ui_policy needs a policy

This is a Write operation as it creates new configuration in ServiceNow that can be modified or removed. The severity is high because UI policies control form behavior and validation across potentially many users and catalog requests, making misconfiguration a significant operational risk.

From the tool's definition Tool is explicitly marked as [Write] and creates a UI policy for a catalog item form. The action is reversible as policies can be modified or deleted, and it does not result in permanent data loss or financial transactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_catalog_ui_policy Rate-limited

create_catalog_ui_policy 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": {
    "create_catalog_ui_policy": {
      "limits": [
        {
          "counter": "create_catalog_ui_policy_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, so you can run agents against it safely.

FAQ

Questions about create_catalog_ui_policy

What does the create_catalog_ui_policy tool do? +

[Write] Create a UI policy for a catalog item form. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_catalog_ui_policy? +

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

What risk level is create_catalog_ui_policy? +

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

Can I rate-limit create_catalog_ui_policy? +

Yes. Add a rate_limit block to the create_catalog_ui_policy 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 create_catalog_ui_policy completely? +

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

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