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, a...
This record as markdown: /tools/2tl-hangar-mcp/hangar-get-data-keys.md
What hangar_get_data_keys does on Hangar
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.
| 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.
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.
Attacks that exploit this kind of access
The rule that runs hangar_get_data_keys 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_get_data_keys, this is the rule to start with:
hangar_get_data_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hangar, apply this rule, and every hangar_get_data_keys call is checked against it from then on.
Questions about 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)만 돌려줍니다. It is categorised as a Read tool in the Hangar MCP Server, which means it retrieves data without modifying state.
hangar_get_data_keys accepts 2 parameters: slug, environment. Required: slug, environment. The full parameter table on this page comes from the server's own tool schema.
Register the Hangar MCP server in PolicyLayer and add a rule for hangar_get_data_keys: 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_get_data_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hangar_get_data_keys 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_get_data_keys. 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_get_data_keys 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.
This server
Across the catalogue