create_scheduled_job
Create a new scheduled script execution job (requires WRITE_ENABLED=true)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/create-scheduled-job.md
What create_scheduled_job does on ServiceNow-MCP
AI agents invoke create_scheduled_job to trigger actions in ServiceNow-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why create_scheduled_job is rated High
Although 'create' implies Write, the primary effect is scheduling future script executions on a ServiceNow instance. Scheduled script execution has Execute-level risk because arbitrary scripts will run repeatedly with potentially wide blast radius. Requires WRITE_ENABLED=true confirms it performs real side effects. Execute > Write per the severity hierarchy.
From the tool's definition 'Create a new scheduled script execution job' — this tool creates a job that will execute scripts on a schedule
Attacks that exploit this kind of access
The rule that runs create_scheduled_job 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 create_scheduled_job, this is the rule to start with:
create_scheduled_job stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 create_scheduled_job call is checked against it from then on.
Questions about create_scheduled_job
Create a new scheduled script execution job (requires WRITE_ENABLED=true). It is categorised as a Execute tool in the ServiceNow-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceNow MCP server in PolicyLayer and add a rule for create_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. Nothing to install.
create_scheduled_job is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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 create_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.
create_scheduled_job 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.
Across the catalogue