list_risk_criteria

List the Impact/Likelihood/Score scale (sn_risk_criteria) used by Risk records — 5 rows per

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/list-risk-criteria.md

WHAT IT DOES

What list_risk_criteria does on ServiceNow-MCP

AI agents call list_risk_criteria 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 list_risk_criteria is rated Low

This tool retrieves configuration metadata (risk scoring criteria) from ServiceNow without modifying, executing operations, or deleting data. It is a straightforward query operation that returns reference data used by risk records. The blast radius of misuse is minimal—an agent could only enumerate existing risk criteria, causing no side effects.

From the tool's definition Tool description explicitly states it 'List[s]' the Impact/Likelihood/Score scale from Risk records, with no modification or deletion capability mentioned. The verb 'list' and the read-only nature of querying metadata scales indicate retrieval only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_risk_criteria Allowed

list_risk_criteria 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": {
    "list_risk_criteria": {}
  }
}

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 list_risk_criteria call is checked against it from then on.

FAQ

Questions about list_risk_criteria

What does the list_risk_criteria tool do? +

List the Impact/Likelihood/Score scale (sn_risk_criteria) used by Risk records — 5 rows per. 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 list_risk_criteria? +

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

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

Can I rate-limit list_risk_criteria? +

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

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

list_risk_criteria 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

aiva_get_churn_risk on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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