# hangar_job_runs

Read-only. Recent runs of one job (name), or of every job when name is omitted (5 each), newest first: status, trigger, times, failure reason. / 잡 실행 기록(읽기 전용).

Agent View of the PolicyLayer registry record for `hangar_job_runs`. HTML page: https://policylayer.com/tools/2tl-hangar-mcp/hangar-job-runs

## Facts

- Tool: `hangar_job_runs`
- Server: Hangar (`@2tl/hangar-mcp`) — https://policylayer.com/tools/2tl-hangar-mcp.md
- Install: `npx -y @2tl/hangar-mcp`
- Homepage: https://www.npmjs.com/package/@2tl/hangar-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | Job name from hangar.json. Omit for every job. |
| `slug` | string | yes | Project slug (= site address). / 프로젝트 slug (사이트 주소) |
| `environment` | string | yes | "preview" or "production". Each has its own releases, database and user accounts. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "hangar_job_runs",
    "arguments": {
      "slug": "<slug>",
      "environment": "<environment>"
    }
  }
}
```

## Why hangar_job_runs is rated High

hangar_job_runs triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents invoke hangar_job_runs to trigger actions in Hangar. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hangar:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hangar_job_runs": {
      "limits": [
        {
          "counter": "hangar_job_runs_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Hangar (10)

- `hangar_whoami` — Destructive — https://policylayer.com/tools/2tl-hangar-mcp/hangar-whoami.md
- `hangar_check_project` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-check-project.md
- `hangar_get_data_keys` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-get-data-keys.md
- `hangar_list_jobs` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-list-jobs.md
- `hangar_list_projects` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-list-projects.md
- `hangar_production_handoff` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-production-handoff.md
- `hangar_release_status` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-release-status.md
- `hangar_activate_preview` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-activate-preview.md
- `hangar_create_project` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-create-project.md
- `hangar_publish` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-publish.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=2tl-hangar-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2tl-hangar-mcp
