list_compliance_controls
List Compliance Controls (sn_compliance_control). Filter by state, category, or the Entity (profile) it protects.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-compliance-controls.md
What list_compliance_controls does on ServiceNow-MCP
AI agents call list_compliance_controls 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_compliance_controls is rated Low
This tool retrieves and queries compliance control data from ServiceNow with no side effects. It only filters and returns information about compliance controls, matching the 'Read' category definition of retrieving or querying data without side effects.
From the tool's definition Tool name includes 'list' and description explicitly states 'List Compliance Controls' with filter capabilities (state, category, Entity). No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs list_compliance_controls 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_compliance_controls, this is the rule to start with:
list_compliance_controls 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_compliance_controls call is checked against it from then on.
Questions about list_compliance_controls
List Compliance Controls (sn_compliance_control). Filter by state, category, or the Entity (profile) it protects. 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_compliance_controls: 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_compliance_controls 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_compliance_controls 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_compliance_controls. 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_compliance_controls 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