list_control_objectives
List Control Objectives (sn_compliance_policy_statement) — sits between Policy and Control.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/list-control-objectives.md
What list_control_objectives does on ServiceNow-MCP
AI agents call list_control_objectives 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_control_objectives is rated Low
This tool retrieves or enumerates Control Objectives from the ServiceNow compliance module. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or executed. Compliance policy statements are typically sensitive in security context but the tool itself only reads existing data, making it a Read category with low severity risk.
From the tool's definition Tool name 'list_control_objectives' and description 'List Control Objectives' indicate a retrieval operation with no modification or deletion. The table reference 'sn_compliance_policy_statement' is a data query target, not an action that modifies data.
Attacks that exploit this kind of access
The rule that runs list_control_objectives 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_control_objectives, this is the rule to start with:
list_control_objectives 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_control_objectives call is checked against it from then on.
Questions about list_control_objectives
List Control Objectives (sn_compliance_policy_statement) — sits between Policy and Control. 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_control_objectives: 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_control_objectives 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_control_objectives 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_control_objectives. 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_control_objectives 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