10 tools from the DevPilot MCP Server, categorised by risk level.
View the DevPilot policy →devpilot_changed Report a file change and check if the dev server reloaded successfully. Call this AFTER editing a file. Returns which service was affected, reload ... 2/5 devpilot_health_check Perform a direct health check on any port. Returns healthy/unhealthy status, HTTP status code, and response time. Works without registering a servi... devpilot_init Auto-detect project structure and generate .devpilot.yaml config. Scans for pyproject.toml, requirements.txt, and package.json to detect frameworks... devpilot_log View recent devpilot events including auto-restarts, crashes, recoveries, and escalations.
Args:
service_name: Filter to a specific se... devpilot_status Check health status of dev server services. Returns live health check results including status, response time, and configuration for all registered... devpilot_run Start and manage a dev server process. Spawns the process, captures stdout, detects reload patterns, monitors health, and auto-recovers from crashe... 4/5 devpilot_stop Gracefully stop managed dev server services. Only stops services that devpilot started. Never kills processes it didn't start.
Args:
n... 3/5 devpilot_up Start all services defined in .devpilot.yaml. Reads the project config and starts each service under supervision with auto-recovery. 3/5 The DevPilot MCP server exposes 10 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the DevPilot server.
DevPilot tools are categorised as Read (5), Write (1), Destructive (1), Execute (3). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept