# 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 활성화는 모든 자격증명에 대해 항상 콘솔 전용입니다.

Agent View of the PolicyLayer registry record for `hangar_whoami`. HTML page: https://policylayer.com/tools/2tl-hangar-mcp/hangar-whoami

## Facts

- Tool: `hangar_whoami`
- Server: Hangar (`@2tl/hangar-mcp`) — https://policylayer.com/tools/2tl-hangar-mcp.md
- Install: `npx -y @2tl/hangar-mcp`
- Homepage: https://www.npmjs.com/package/@2tl/hangar-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "hangar_whoami",
    "arguments": {}
  }
}
```

## 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 signals: Bulk/mass operation — affects multiple targets

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hangar:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "hangar_whoami"
  ]
}
```

## Other tools on Hangar (10)

- `hangar_job_runs` — Execute — https://policylayer.com/tools/2tl-hangar-mcp/hangar-job-runs.md
- `hangar_check_project` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-check-project.md
- `hangar_get_data_keys` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-get-data-keys.md
- `hangar_list_jobs` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-list-jobs.md
- `hangar_list_projects` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-list-projects.md
- `hangar_production_handoff` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-production-handoff.md
- `hangar_release_status` — Read — https://policylayer.com/tools/2tl-hangar-mcp/hangar-release-status.md
- `hangar_activate_preview` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-activate-preview.md
- `hangar_create_project` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-create-project.md
- `hangar_publish` — Write — https://policylayer.com/tools/2tl-hangar-mcp/hangar-publish.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2tl-hangar-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2tl-hangar-mcp
