list_credential_aliases

List connection and credential aliases used by integrations

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/list-credential-aliases.md

WHAT IT DOES

What list_credential_aliases does on ServiceNow MCP Server

AI agents call list_credential_aliases to retrieve information from ServiceNow MCP Server 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_credential_aliases is rated Low

This is a Read operation—it retrieves information about credential aliases used by integrations with no side effects. However, severity is elevated to 'high' because exposing credential aliases could leak information about integration patterns, security architecture, and potential attack surface.

From the tool's definition Tool name 'list_credential_aliases' and description 'List connection and credential aliases used by integrations' indicate retrieval of credential metadata without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_credential_aliases safely

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

list_credential_aliases Allowed

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

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

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

FAQ

Questions about list_credential_aliases

What does the list_credential_aliases tool do? +

List connection and credential aliases used by integrations. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_credential_aliases? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for list_credential_aliases: 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 Server. Nothing to install.

What risk level is list_credential_aliases? +

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

Can I rate-limit list_credential_aliases? +

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

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

list_credential_aliases is provided by the ServiceNow MCP Server MCP server (@aartiq/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 MCP Server, and thousands of servers like it.

This server

All 365 ServiceNow MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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