# pre_flight_check

Security pre-flight check for local file changes BEFORE committing. Run this whenever you are about to suggest git commit, git push, or open a pull request — especially when changes touch auth, secrets, SQL queries, package.json / requirements.txt, or environment variables. Returns CLEAR or BLOCKED with specific findings and remediation steps.

Agent View of the PolicyLayer registry record for `pre_flight_check`. HTML page: https://policylayer.com/tools/com-graneth-mcp-server/pre-flight-check

## Facts

- Tool: `pre_flight_check`
- Server: Mcp Server (`@graneth/mcp-server`) — https://policylayer.com/tools/com-graneth-mcp-server.md
- Install: `npx -y @graneth/mcp-server`
- Homepage: https://github.com/zubovartemiy/graneth-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `files` | array | yes | Files staged for commit (path + content) |
| `context` | string | no | What these changes do (helps with triage) |

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": "pre_flight_check",
    "arguments": {
      "files": []
    }
  }
}
```

## Why pre_flight_check is rated Low

This is a scanning and reporting tool. It inspects files and detects issues (hallucinated packages, hardcoded secrets) but does not modify data, execute arbitrary code, delete files, or perform financial operations.

From the tool's own definition: "Tool performs a 'Security pre-flight check' that 'Returns CLEAR or BLOCKED with specific findings' — it scans and reports on local file changes without modifying or executing code."

Risk signals: Accepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)

## Use case

AI agents call pre_flight_check to retrieve information from Mcp Server 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 Mcp Server:

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

## Other tools on Mcp Server (3)

- `scan_repository` — Execute — https://policylayer.com/tools/com-graneth-mcp-server/scan-repository.md
- `get_findings` — Read — https://policylayer.com/tools/com-graneth-mcp-server/get-findings.md
- `auto_remediate` — Write — https://policylayer.com/tools/com-graneth-mcp-server/auto-remediate.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=com-graneth-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-graneth-mcp-server