Report a file change and check if the dev server reloaded successfully. Call this AFTER editing a file. Returns which service was affected, reload status (reloaded/reload_failed/timeout), and health. This is the primary feedback loop for AI coders. Args: filepath: Path of the changed file relativ...
Risk signalsAccepts file system path (filepath) · Admin/system-level operation
Part of the DevPilot server.
Free to start. No card required.
AI agents call devpilot_changed to retrieve information from DevPilot without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though devpilot_changed only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"devpilot_changed": {}
}
}See the full DevPilot policy for all 10 tools.
These attack patterns abuse exactly the kind of access devpilot_changed gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Report a file change and check if the dev server reloaded successfully. Call this AFTER editing a file. Returns which service was affected, reload status (reloaded/reload_failed/timeout), and health. This is the primary feedback loop for AI coders. Args: filepath: Path of the changed file relative to project root. verify_endpoint: Optional HTTP endpoint to hit after reload, e.g. "/api/hello". timeout: Max seconds to wait for reload detection. Default 15.. It is categorised as a Read tool in the DevPilot MCP Server, which means it retrieves data without modifying state.
Register the DevPilot MCP server in PolicyLayer and add a rule for devpilot_changed: 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_changed 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 devpilot_changed 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_changed. 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_changed 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.