hangar_check_project
Check an app directory before publishing, offline: hangar.json validity, the build output directory and entrypoint, tables without row-level security in migrations, and job bundle problems. With init: true, creates hangar.json when it is missing (never overwrites). Fix every finding with level "e...
This record as markdown: /tools/2tl-hangar-mcp/hangar-check-project.md
What hangar_check_project does on Hangar
AI agents call hangar_check_project 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 |
|---|---|---|---|
init | boolean | — | Create hangar.json if it does not exist. Default false. |
projectDir | string | Yes | The app's directory (absolute path recommended; relative paths resolve against the server's working directory). Must be inside the folder the AI tool was starte |
Parameters from the server's own tool schema.
Why hangar_check_project is rated Low
Even though hangar_check_project 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hangar_check_project 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_check_project, this is the rule to start with:
hangar_check_project 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_check_project call is checked against it from then on.
Questions about hangar_check_project
Check an app directory before publishing, offline: hangar.json validity, the build output directory and entrypoint, tables without row-level security in migrations, and job bundle problems. With init: true, creates hangar.json when it is missing (never overwrites). Fix every finding with level "error" before hangar_publish. / 발행 전 점검(hangar.json, 빌드 산출물, RLS 경고, 잡 번들). It is categorised as a Read tool in the Hangar MCP Server, which means it retrieves data without modifying state.
hangar_check_project accepts 2 parameters: init, projectDir. Required: projectDir. 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_check_project: 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_check_project 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_check_project 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_check_project. 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_check_project 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