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. / 잡 실행 기록(읽기 전용).
This record as markdown: /tools/2tl-hangar-mcp/hangar-job-runs.md
What hangar_job_runs does on Hangar
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | 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.
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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hangar_job_runs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hangar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hangar_job_runs, this is the rule to start with:
hangar_job_runs 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 Hangar, apply this rule, and every hangar_job_runs call is checked against it from then on.
Questions about 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. / 잡 실행 기록(읽기 전용). It is categorised as a Execute tool in the Hangar MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
hangar_job_runs accepts 3 parameters: name, slug, environment. Required: slug, environment. The full parameter table on this page comes from the server's own tool schema.
Register the Hangar MCP server in PolicyLayer and add a rule for hangar_job_runs: 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 Hangar. Nothing to install.
hangar_job_runs 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 hangar_job_runs 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 hangar_job_runs. 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.
hangar_job_runs is provided by the Hangar MCP server (@2tl/hangar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hangar, and thousands of servers like it.
Across the catalogue