list_event_registry
List registered event definitions in the ServiceNow event registry
This record as markdown: /tools/servicenow-mcp-server/list-event-registry.md
What list_event_registry does on ServiceNow MCP Server
AI agents call list_event_registry 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.
Why list_event_registry is rated Low
The tool performs a read-only query operation that returns information about registered events. There are no side effects, data modifications, deletions, financial transactions, or code execution involved. The blast radius of misuse is minimal — an attacker would only gain visibility into what events are defined in the system, which may expose some internal ServiceNow architecture but does not enable direct harm.
From the tool's definition Tool name is 'list_event_registry' and description states 'List registered event definitions in the ServiceNow event registry' — this retrieves or queries a list of event definitions without modifying any data.
Attacks that exploit this kind of access
The rule that runs list_event_registry 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_event_registry, this is the rule to start with:
list_event_registry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow MCP Server, apply this rule, and every list_event_registry call is checked against it from then on.
Questions about list_event_registry
List registered event definitions in the ServiceNow event registry. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for list_event_registry: 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.
list_event_registry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_event_registry 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.
Set action: deny in the PolicyLayer policy for list_event_registry. 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.
list_event_registry 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.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue