get_scheduled_job
Get full details of a scheduled job by sys_id or name
This record as markdown: /tools/servicenow-mcp-server/get-scheduled-job.md
What get_scheduled_job does on ServiceNow MCP Server
AI agents call get_scheduled_job to retrieve information from ServiceNow MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_scheduled_job is rated Low
This tool queries and retrieves metadata about a scheduled job without executing it, modifying it, or triggering any side effects. It is a straightforward read operation that returns information based on sys_id or name lookup. Severity is low because exposure of this tool alone does not enable destructive or consequential actions—it only reveals job configuration details.
From the tool's definition Tool name and description indicate retrieval of details: 'Get full details of a scheduled job'. The verb 'get' and 'details' are purely informational with no modification or execution of the job itself.
Attacks that exploit this kind of access
The rule that runs get_scheduled_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_scheduled_job, this is the rule to start with:
get_scheduled_job 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 Server, apply this rule, and every get_scheduled_job call is checked against it from then on.
Questions about get_scheduled_job
Get full details of a scheduled job by sys_id or name. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for get_scheduled_job: 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 Server. Nothing to install.
get_scheduled_job 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_scheduled_job 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_scheduled_job. 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_scheduled_job is provided by the ServiceNow MCP Server MCP server (@aartiq/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue