check_app_upgrade

Compare the installed version of a scoped app (from sys_scope on the instance) against the

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/check-app-upgrade.md

WHAT IT DOES

What check_app_upgrade does on ServiceNow-MCP

AI agents call check_app_upgrade to retrieve information from ServiceNow-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_app_upgrade is rated Low

Compares versions without modification; information retrieval only, no side effects.

From the tool's definition Compare the installed version of a scoped app against

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_app_upgrade 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 check_app_upgrade, this is the rule to start with:

check_app_upgrade Allowed

check_app_upgrade is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_app_upgrade": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about check_app_upgrade

What does the check_app_upgrade tool do? +

Compare the installed version of a scoped app (from sys_scope on the instance) against the. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_app_upgrade? +

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

check_app_upgrade is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_app_upgrade? +

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

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

check_app_upgrade 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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →