Start all services defined in .devpilot.yaml. Reads the project config and starts each service under supervision with auto-recovery.
Part of the DevPilot server.
Free to start. No card required.
AI agents invoke devpilot_up to trigger processes or run actions in DevPilot. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
devpilot_up can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"devpilot_up": {
"limits": [
{
"counter": "devpilot_up_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full DevPilot policy for all 10 tools.
These attack patterns abuse exactly the kind of access devpilot_up gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Start all services defined in .devpilot.yaml. Reads the project config and starts each service under supervision with auto-recovery.. It is categorised as a Execute tool in the DevPilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DevPilot MCP server in PolicyLayer and add a rule for devpilot_up: 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 DevPilot. Nothing to install.
devpilot_up is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the devpilot_up 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 devpilot_up. 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.
devpilot_up is provided by the DevPilot MCP server (benzsevern/devpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 DevPilot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.