hangar_whoami
Check the automation key: its name, workspace, expiry, how many projects it has created out of its limit, and how many projects it reaches. Production activation, rollback, pause/resume and deploy cancel/retry are console-only for every credential — never a per-key property. Call this first. / 키 ...
This record as markdown: /tools/2tl-hangar-mcp/hangar-whoami.md
What hangar_whoami does on Hangar
AI agents call hangar_whoami to permanently remove resources in Hangar, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why hangar_whoami is rated Critical
An AI agent that decides to call hangar_whoami doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Hangar is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hangar_whoami 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_whoami, this is the rule to start with:
hangar_whoami is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hangar, apply this rule, and every hangar_whoami call is checked against it from then on.
Questions about hangar_whoami
Check the automation key: its name, workspace, expiry, how many projects it has created out of its limit, and how many projects it reaches. Production activation, rollback, pause/resume and deploy cancel/retry are console-only for every credential — never a per-key property. Call this first. / 키 확인: 이름·워크스페이스·만료·생성 수/상한. production 활성화는 모든 자격증명에 대해 항상 콘솔 전용입니다. It is categorised as a Destructive tool in the Hangar MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hangar MCP server in PolicyLayer and add a rule for hangar_whoami: 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_whoami is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hangar_whoami 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_whoami. 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_whoami 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