get_control_objective
Get full details of a single Control Objective by sys_id.
This record as markdown: /tools/tedorigawa001-servicenow-mcp/get-control-objective.md
What get_control_objective does on ServiceNow-MCP
AI agents call get_control_objective 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 get_control_objective is rated Low
This tool performs a read-only operation by retrieving details of a Control Objective record identified by its system ID. It has no capability to modify, delete, execute, or commit financial actions. The blast radius of misuse is minimal—an agent could over-query or access sensitive control objectives, but cannot cause data loss or irreversible changes.
From the tool's definition Tool name 'get_control_objective' with description 'Get full details of a single Control Objective by sys_id' indicates a retrieval operation that queries and returns data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_control_objective 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 get_control_objective, this is the rule to start with:
get_control_objective 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 get_control_objective call is checked against it from then on.
Questions about get_control_objective
Get full details of a single Control Objective by sys_id. 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 get_control_objective: 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.
get_control_objective 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 get_control_objective 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 get_control_objective. 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.
get_control_objective 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