hangar_release_status
Read one environment's release state: the desired release and revision, the release actually serving, and the in-flight deployment if any. / 환경의 현재 대상·서빙 중 릴리스·진행 중 배포.
This record as markdown: /tools/2tl-hangar-mcp/hangar-release-status.md
What hangar_release_status does on Hangar
AI agents call hangar_release_status to retrieve information from Hangar without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
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_release_status is rated Low
Even though hangar_release_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs hangar_release_status 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_release_status, this is the rule to start with:
hangar_release_status is read-only, so it stays allowed. 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_release_status call is checked against it from then on.
Questions about hangar_release_status
Read one environment's release state: the desired release and revision, the release actually serving, and the in-flight deployment if any. / 환경의 현재 대상·서빙 중 릴리스·진행 중 배포. It is categorised as a Read tool in the Hangar MCP Server, which means it retrieves data without modifying state.
hangar_release_status accepts 2 parameters: 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_release_status: 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_release_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hangar_release_status 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_release_status. 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_release_status 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.
This server
Across the catalogue