scheduled_job_run · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What scheduled_job_run does on ServiceNow MCP Server

AI agents invoke scheduled_job_run to trigger actions in ServiceNow MCP Server. 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 IT NEEDS A POLICY

Why scheduled_job_run needs a policy

This tool executes scheduled jobs whose effects are dependent on the argument passed (which job to run). While not inherently destructive, executing arbitrary scheduled jobs in an enterprise ITSM system carries significant risk: jobs may perform data modifications, trigger integrations with external systems, send notifications, or execute scripts with unintended consequences.

From the tool's definition Tool name 'scheduled_job_run' combined with description 'Execute a scheduled job immediately' indicates execution of external operations. The term 'Execute' in the description is explicit.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scheduled_job_run Rate-limited

scheduled_job_run 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scheduled_job_run": {
      "limits": [
        {
          "counter": "scheduled_job_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceNow MCP Server, so you can run agents against it safely.

FAQ

Questions about scheduled_job_run

What does the scheduled_job_run tool do? +

Execute a scheduled job immediately. It is categorised as a Execute tool in the ServiceNow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on scheduled_job_run? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for scheduled_job_run: 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.

What risk level is scheduled_job_run? +

scheduled_job_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit scheduled_job_run? +

Yes. Add a rate_limit block to the scheduled_job_run 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.

How do I block scheduled_job_run completely? +

Set action: deny in the PolicyLayer policy for scheduled_job_run. 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.

What MCP server provides scheduled_job_run? +

scheduled_job_run is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.