Diagnose a failing V1 API test and propose an action. Triggered when: * keploy test-gen run exited non-zero in a fresh agent session (the dev's code changed since the test was authored). * A PR Keploy comment surfaced a failure and the dev says "fix it". Action classes (mutually exclusive — the C...
Part of the Keploy server.
Free to start. No card required.
AI agents invoke devloop_self_heal to trigger processes or run actions in Keploy. 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.
devloop_self_heal 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": {
"devloop_self_heal": {
"limits": [
{
"counter": "devloop_self_heal_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Keploy policy for all 103 tools.
These attack patterns abuse exactly the kind of access devloop_self_heal 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.
Diagnose a failing V1 API test and propose an action. Triggered when: * keploy test-gen run exited non-zero in a fresh agent session (the dev's code changed since the test was authored). * A PR Keploy comment surfaced a failure and the dev says "fix it". Action classes (mutually exclusive — the CLI picks one): * auto_update — diff is an unambiguous rename or refactor (same value moves to a different field name, or a step name changed without semantic effect). The AI can apply the proposed patch directly. * ask_user — the diff is ambiguous (a field disappeared, a value changed in a way that could be intentional). The AI surfaces the proposed alternatives and waits for the dev. * revert_suggestion — the diff looks like a real regression (status code drifted, expected response shape is incompatible). The AI suggests the dev revert the offending code; does NOT silently update the test. HARD RULE: never rewrite an assertion to make a red test green. The CLI enforces this by refusing to emit an auto_update for any change that weakens an assertion. The AI must also enforce this — if the CLI's proposal includes "change expected_string from X to Y" where X was the correct contract, REJECT the proposal and ask the dev.. It is categorised as a Execute tool in the Keploy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Keploy MCP server in PolicyLayer and add a rule for devloop_self_heal: 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 Keploy. Nothing to install.
devloop_self_heal 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 devloop_self_heal 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 devloop_self_heal. 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.
devloop_self_heal is provided by the Keploy MCP server (https://api.keploy.io/client/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 103 Keploy 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.