# job_status

A read tool on the Adr Fpga Bootstrap MCP server.

Agent View of the PolicyLayer registry record for `job_status`. HTML page: https://policylayer.com/tools/adr-fpga-bootstrap/job-status

## Facts

- Tool: `job_status`
- Server: Adr Fpga Bootstrap (`zxyyz/adr-fpga-bootstrap`) — https://policylayer.com/tools/adr-fpga-bootstrap.md
- Homepage: https://github.com/zxyyz/adr-fpga-bootstrap
- 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": "job_status",
    "arguments": {}
  }
}
```

## Why job_status is rated Low

Status checks are read-only operations that retrieve information about existing jobs without modifying, executing, or destroying anything. The absence of a description lowers confidence slightly, but the naming convention and context of related tools strongly suggest a non-destructive query operation. No side effects or resource consumption beyond data retrieval is expected.

From the tool's own definition: "Tool name 'job_status' with empty description suggests it retrieves the current state of a planning job. The name pattern and sibling tools (create_or_resume_planning_job, get_plan_preview, get_change_file) indicate this is a query/status-checking operation."

## Use case

AI agents call job_status to retrieve information from Adr Fpga Bootstrap 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 Adr Fpga Bootstrap:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "job_status": {}
  }
}
```

## Other tools on Adr Fpga Bootstrap (38)

- `job_cancel` — Destructive — https://policylayer.com/tools/adr-fpga-bootstrap/job-cancel.md
- `sources_remove` — Destructive — https://policylayer.com/tools/adr-fpga-bootstrap/sources-remove.md
- `build` — Execute — https://policylayer.com/tools/adr-fpga-bootstrap/build.md
- `messages` — Other — https://policylayer.com/tools/adr-fpga-bootstrap/messages.md
- `file_read` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/file-read.md
- `host_status` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/host-status.md
- `job_artifacts` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/job-artifacts.md
- `job_list` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/job-list.md
- `sources_list` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/sources-list.md
- `sync_status` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/sync-status.md
- `add_include_dirs` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/add-include-dirs.md
- `agent_ensure` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/agent-ensure.md
- `file_grep` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/file-grep.md
- `ip_create` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-create.md
- `ip_generate` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-generate.md
- `ip_upgrade` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-upgrade.md
- `job_events` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/job-events.md
- `job_logs` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/job-logs.md
- `project_close` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-close.md
- `project_info` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-info.md
- `project_open` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-open.md
- `project_unlock` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-unlock.md
- `report_cdc` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-cdc.md
- `report_clocks` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-clocks.md
- `report_diff` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-diff.md
- `report_drc` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-drc.md
- `report_methodology` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-methodology.md
- `report_power` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-power.md
- `report_timing_paths` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-timing-paths.md
- `report_timing_summary` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-timing-summary.md
- …and 8 more: https://policylayer.com/tools/adr-fpga-bootstrap.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=adr-fpga-bootstrap · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adr-fpga-bootstrap