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

hangar_activate_preview

Switch the PREVIEW site to a release published to preview, then wait (up to ~3 minutes) until it is actually serving. Returns the preview URL. Preview only: there is no production activation here. / preview 를 이 릴리스로 전환하고 서빙될 때까지 기다립니다.

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

This record as markdown: /tools/2tl-hangar-mcp/hangar-activate-preview.md

What hangar_activate_preview does on Hangar

AI agents use hangar_activate_preview to create or update resources in Hangar, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hangar environment.

ParameterTypeRequiredDescription
slug string Yes Project slug (= site address). / 프로젝트 slug (사이트 주소)
releaseId string Yes Release id returned by hangar_publish.

Parameters from the server's own tool schema.

Why hangar_activate_preview is rated Medium

An AI agent can call hangar_activate_preview faster than any human can review: one bad instruction and it creates or modifies resources in Hangar by the hundred, each call as confident as the last.

Questions about hangar_activate_preview

What does the hangar_activate_preview tool do? +

Switch the PREVIEW site to a release published to preview, then wait (up to ~3 minutes) until it is actually serving. Returns the preview URL. Preview only: there is no production activation here. / preview 를 이 릴리스로 전환하고 서빙될 때까지 기다립니다. It is categorised as a Write tool in the Hangar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does hangar_activate_preview accept? +

hangar_activate_preview accepts 2 parameters: slug, releaseId. Required: slug, releaseId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hangar_activate_preview? +

Register the Hangar MCP server in PolicyLayer and add a rule for hangar_activate_preview: 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_activate_preview? +

hangar_activate_preview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hangar_activate_preview? +

Yes. Add a rate_limit block to the hangar_activate_preview 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_activate_preview completely? +

Set action: deny in the PolicyLayer policy for hangar_activate_preview. 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_activate_preview? +

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