# snow_job_status Unified read-only visibility into ServiceNow background work. Spans sys_trigger (scheduled-job triggers), sys_progress_worker (background workers for transforms, imports, large operations), and sys_execution_tracker (fix-script and async-operation trackers). Actions: - list_active — list currently running/queued work across triggers, workers, and trackers - get_status — fetch the full record for a single job/worker/tracker by sys_id - get_history — historical runs for a specific scheduled job (sys_trigger), bounded by limit and time window - get_errors — surface recent failed/errored runs across the three sources Use when: the agent needs real-time situational awareness of what is running on the instance, debugging a slow transform, or auditing why a scheduled job did not fire. Companion to snow_trigger_scheduled_job for starting jobs and snow_scheduled_job_manage for defining them. Returns: per-source arrays of normalized records with sys_id, name, state, progress, started_at, completed_at, and source-specific fields. All operations are read-only Table API queries. Agent View of the PolicyLayer registry record for `snow_job_status`. HTML page: https://policylayer.com/tools/serac/snow-job-status ## Facts - Tool: `snow_job_status` - Server: Serac (`serac-labs/serac`) — https://policylayer.com/tools/serac.md - Homepage: https://github.com/serac-labs/serac - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Allowed ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "snow_job_status", "arguments": {} } } ``` ## Why snow_job_status is rated Low This tool provides visibility into ServiceNow background job execution state and history without the ability to modify, delete, or trigger work. It is purely informational, retrieving status and error data from existing job records. The read-only nature and absence of side effects place it firmly in the Read category with low severity. From the tool's own definition: "Tool description explicitly states 'read-only visibility' and all actions are query/retrieval operations: list_active, get_status, get_history, get_errors—none create, modify, delete, or execute operations." ## Use case AI agents call snow_job_status to retrieve information from Serac without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere. ## Recommended policy (PolicyLayer) Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Serac: ```json { "version": "1", "default": "deny", "tools": { "snow_job_status": {} } } ``` ## Other tools on Serac (431) - `snow_cleanup_test_artifacts` — Destructive — https://policylayer.com/tools/serac/snow-cleanup-test-artifacts.md - `snow_delete_attachment` — Destructive — https://policylayer.com/tools/serac/snow-delete-attachment.md - `snow_inbound_email_action` — Destructive — https://policylayer.com/tools/serac/snow-inbound-email-action.md - `snow_pa_indicator_manage` — Destructive — https://policylayer.com/tools/serac/snow-pa-indicator-manage.md - `snow_rollback_deployment` — Destructive — https://policylayer.com/tools/serac/snow-rollback-deployment.md - `snow_workflow_transition` — Destructive — https://policylayer.com/tools/serac/snow-workflow-transition.md - `enterprise_tool_execute` — Execute — https://policylayer.com/tools/serac/enterprise-tool-execute.md - `snow_auto_resolve_incident` — Execute — https://policylayer.com/tools/serac/snow-auto-resolve-incident.md - `snow_automate_threat_response` — Execute — https://policylayer.com/tools/serac/snow-automate-threat-response.md - `snow_batch_request` — Execute — https://policylayer.com/tools/serac/snow-batch-request.md - `snow_change_manage` — Execute — https://policylayer.com/tools/serac/snow-change-manage.md - `snow_cicd_deploy` — Execute — https://policylayer.com/tools/serac/snow-cicd-deploy.md - `snow_collect_metric` — Execute — https://policylayer.com/tools/serac/snow-collect-metric.md - `snow_confirm_script_execution` — Execute — https://policylayer.com/tools/serac/snow-confirm-script-execution.md - `snow_convert_es6_to_es5` — Execute — https://policylayer.com/tools/serac/snow-convert-es6-to-es5.md - `snow_convert_to_es5` — Execute — https://policylayer.com/tools/serac/snow-convert-to-es5.md - `snow_create_mobile_action` — Execute — https://policylayer.com/tools/serac/snow-create-mobile-action.md - `snow_create_vulnerability_scan` — Execute — https://policylayer.com/tools/serac/snow-create-vulnerability-scan.md - `snow_custom_api` — Execute — https://policylayer.com/tools/serac/snow-custom-api.md - `snow_elevate_role` — Execute — https://policylayer.com/tools/serac/snow-elevate-role.md - `snow_employee_offboarding` — Execute — https://policylayer.com/tools/serac/snow-employee-offboarding.md - `snow_employee_onboarding` — Execute — https://policylayer.com/tools/serac/snow-employee-onboarding.md - `snow_execute_atf_test` — Execute — https://policylayer.com/tools/serac/snow-execute-atf-test.md - `snow_execute_script` — Execute — https://policylayer.com/tools/serac/snow-execute-script.md - `snow_execute_security_playbook` — Execute — https://policylayer.com/tools/serac/snow-execute-security-playbook.md - `snow_execute_transform` — Execute — https://policylayer.com/tools/serac/snow-execute-transform.md - `snow_fluent_build` — Execute — https://policylayer.com/tools/serac/snow-fluent-build.md - `snow_fluent_install` — Execute — https://policylayer.com/tools/serac/snow-fluent-install.md - `snow_fluent_transform` — Execute — https://policylayer.com/tools/serac/snow-fluent-transform.md - `snow_github_deploy` — Execute — https://policylayer.com/tools/serac/snow-github-deploy.md - …and 401 more: https://policylayer.com/tools/serac.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=serac · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/serac