List UI Actions (buttons, context menus, related links) for a table (requires SCRIPTING_ENABLED=true)
AI agents call list_ui_actions to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about UI elements available for a table—buttons, menus, and links—rather than modifying or executing them. It is fundamentally a query/enumeration operation.
From the tool's definition Tool is named 'list_ui_actions' and described as listing UI Actions (buttons, context menus, related links) for a table. The 'list' verb and action of retrieving/enumerating UI elements indicates a read operation with no side effects on data.
Attacks that exploit this kind of access
List UI Actions (buttons, context menus, related links) for a table (requires SCRIPTING_ENABLED=true). It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for list_ui_actions: 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.
list_ui_actions 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_ui_actions 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_ui_actions. 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_ui_actions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →