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 BLOCK...
This record as markdown: /tools/com-graneth-mcp-server/pre-flight-check.md
What pre_flight_check does on Mcp Server
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
files | array | Yes | Files staged for commit (path + content) |
context | string | — | What these changes do (helps with triage) |
Parameters from the server's own tool schema.
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 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 signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Attacks that exploit this kind of access
The rule that runs pre_flight_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pre_flight_check, this is the rule to start with:
pre_flight_check 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 Mcp Server, apply this rule, and every pre_flight_check call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
pre_flight_check accepts 2 parameters: files, context. Required: files. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for pre_flight_check: 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 Mcp Server. Nothing to install.
pre_flight_check 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 pre_flight_check 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 pre_flight_check. 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.
pre_flight_check is provided by the Mcp Server MCP server (@graneth/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Server, and thousands of servers like it.
This server
Across the catalogue