New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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. / 환경의 현재 대상·서빙 중 릴리스·진행 중 배포.

SERVERHangar SOURCE@2tl/hangar-mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about hangar_release_status

What does the hangar_release_status tool do? +

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.

What parameters does hangar_release_status accept? +

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.

How do I enforce a policy on hangar_release_status? +

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.

What risk level is hangar_release_status? +

hangar_release_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hangar_release_status? +

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.

How do I block hangar_release_status completely? +

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.

What MCP server provides hangar_release_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Hangar's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.