# hangar_get_data_keys

Read the public data-layer keys for one environment: apiUrl (pass to createClient) and the anon key. Only these two — the service_role key is never available here. Preview and production have different databases and different keys: a production build must use the production keys. / 공개 키(apiUrl, anonKey)만 돌려줍니다.

Agent View of the PolicyLayer registry record for `hangar_get_data_keys`. HTML page: https://policylayer.com/tools/2tl-hangar-mcp/hangar-get-data-keys

## Facts

- Tool: `hangar_get_data_keys`
- 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: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `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.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "hangar_get_data_keys",
    "arguments": {
      "slug": "<slug>",
      "environment": "<environment>"
    }
  }
}
```

## Why hangar_get_data_keys is rated Low

Even though hangar_get_data_keys 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.

## Use case

AI agents call hangar_get_data_keys 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.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "hangar_get_data_keys": {}
  }
}
```

## Other tools on Hangar (10)

- `hangar_whoami` — Destructive — https://policylayer.com/tools/2tl-hangar-mcp/hangar-whoami.md
- `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_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
