update_ui_action

Update an existing UI Action (requires SCRIPTING_ENABLED=true)

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/update-ui-action.md

WHAT IT DOES

What update_ui_action does on ServiceNow-MCP

AI agents invoke update_ui_action to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why update_ui_action is rated High

UI Actions in ServiceNow are script-bearing objects that execute server-side or client-side code when triggered. Updating a UI Action effectively modifies executable code/logic within the platform. Because the tool touches scripted artifacts (SCRIPTING_ENABLED requirement confirms this), it falls under Execute rather than plain Write.

From the tool's definition 'Update an existing UI Action (requires SCRIPTING_ENABLED=true)' — modifies UI Actions which contain executable scripts, and explicitly requires scripting to be enabled

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_ui_action safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_ui_action, this is the rule to start with:

update_ui_action Rate-limited

update_ui_action stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_ui_action": {
      "limits": [
        {
          "counter": "update_ui_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every update_ui_action call is checked against it from then on.

FAQ

Questions about update_ui_action

What does the update_ui_action tool do? +

Update an existing UI Action (requires SCRIPTING_ENABLED=true). It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on update_ui_action? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for update_ui_action: 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 update_ui_action? +

update_ui_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit update_ui_action? +

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

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

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

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →