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

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. / 키 ...

SERVERHangar SOURCE@2tl/hangar-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about hangar_whoami

What does the hangar_whoami tool do? +

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.

How do I enforce a policy on hangar_whoami? +

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.

What risk level is hangar_whoami? +

hangar_whoami is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit hangar_whoami? +

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.

How do I block hangar_whoami completely? +

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.

What MCP server provides hangar_whoami? +

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.

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