High-risk tools in DevPilot
3 of the 10 tools in DevPilot are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
devpilot_runExecute 4/5Start and manage a dev server process. Spawns the process, captures stdout, detects reload patterns, monitors health, and auto-recovers from crashes. Supports FastAPI, Flask, Dj...
-
devpilot_stopExecute 3/5Gracefully stop managed dev server services. Only stops services that devpilot started. Never kills processes it didn't start. Args: name: Name of a specific servic...
-
devpilot_upExecute 3/5Start all services defined in .devpilot.yaml. Reads the project config and starts each service under supervision with auto-recovery.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on DevPilot
Enforce policy on DevPilot
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init