update_portal_widget · ServiceNow- MCP: Risk & Policy

WHAT IT DOES

What update_portal_widget does on ServiceNow-MCP

AI agents use update_portal_widget 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 update_portal_widget needs a policy

This tool modifies portal widget configurations reversibly (widgets can be reconfigured or reverted). It does not delete data permanently, execute arbitrary code, trigger financial transactions, or create side effects beyond UI/config changes. The scope is limited to a single portal widget update.

From the tool's definition Tool name is 'update_portal_widget' and description states 'Update an existing Service Portal widget' — indicates modification of existing configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_portal_widget Rate-limited

update_portal_widget 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_portal_widget": {
      "limits": [
        {
          "counter": "update_portal_widget_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 update_portal_widget

What does the update_portal_widget tool do? +

Update an existing Service Portal widget\. 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 update_portal_widget? +

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

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

Can I rate-limit update_portal_widget? +

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

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

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