list_policy_exceptions
List Policy Exceptions (sn_compliance_policy_exception). Filter by state.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-policy-exceptions.md
What list_policy_exceptions does on ServiceNow-MCP
AI agents call list_policy_exceptions 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.
Why list_policy_exceptions is rated Low
This tool retrieves and filters existing policy exception records from ServiceNow's compliance module. It performs a read-only query operation with no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an attacker could enumerate policy exceptions to understand compliance posture, but cannot modify or delete records through this tool alone.
From the tool's definition Tool is named 'list_policy_exceptions' and explicitly described as 'List' with ability to 'Filter by state'. The action is a query/retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
The rule that runs list_policy_exceptions 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_policy_exceptions, this is the rule to start with:
list_policy_exceptions 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, apply this rule, and every list_policy_exceptions call is checked against it from then on.
Questions about list_policy_exceptions
List Policy Exceptions (sn_compliance_policy_exception). Filter by state. 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_policy_exceptions: 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_policy_exceptions 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_policy_exceptions 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_policy_exceptions. 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_policy_exceptions 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue