list_process_automations

List Process Automation Designer playbooks and processes

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-process-automations.md

WHAT IT DOES

What list_process_automations does on ServiceNow-MCP

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

This tool queries and returns information about existing process automations without modifying, deleting, or executing anything. It is a passive read operation on ServiceNow's Process Automation Designer configuration. The blast radius is minimal — an AI agent misusing this tool could only over-query or enumerate processes, not cause data loss or unauthorized changes.

From the tool's definition Tool name contains 'list' and description states 'List Process Automation Designer playbooks and processes' — a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_process_automations Allowed

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

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

FAQ

Questions about list_process_automations

What does the list_process_automations tool do? +

List Process Automation Designer playbooks and processes. 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_process_automations? +

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

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

Can I rate-limit list_process_automations? +

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

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

list_process_automations 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_list_affiliates 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 →