List installed ServiceNow scoped applications and active plugins. Args: - search (string): Filter by application name or scope prefix - include_global (boolean): Include the global scope app (default: false) - active_only (boolean): Only return active applications (default: true) - limit / offset...
AI agents call servicenow_list_applications to retrieve information from Servicenow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing application metadata without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius if misused by an AI agent—worst case being information disclosure about installed applications.
From the tool's definition Tool "lists installed ServiceNow scoped applications and active plugins" with filtering and pagination capabilities. Returns metadata (name, scope, version, vendor, status) with no modification or deletion of data.
Attacks that exploit this kind of access
List installed ServiceNow scoped applications and active plugins. Args: - search (string): Filter by application name or scope prefix - include_global (boolean): Include the global scope app (default: false) - active_only (boolean): Only return active applications (default: true) - limit / offset: Pagination - response_format: Output format Returns: Applications with name, scope, version, vendor, and status Examples: - List all custom applications → active_only=true, include_global=false - Find ITSM-related apps → search=. It is categorised as a Read tool in the Servicenow MCP Server, which means it retrieves data without modifying state.
Register the Servicenow MCP server in PolicyLayer and add a rule for servicenow_list_applications: 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. Nothing to install.
servicenow_list_applications 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 servicenow_list_applications 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 servicenow_list_applications. 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.
servicenow_list_applications is provided by the Servicenow MCP server (kylburns89/servicenow-mcp-server). 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 →