Report the gap between the app's OpenAPI spec and its V1 API-tests coverage. Reuses the existing schema-coverage endpoint that get_coverage_gaps consumes, but frames the result for V1: which endpoints are uncovered, the recommended order to generate tests for them next (highest-fan-in first), and...
Part of the Keploy server.
Free to start. No card required.
AI agents invoke devloop_schema_drift_report 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_schema_drift_report 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_schema_drift_report": {
"limits": [
{
"counter": "devloop_schema_drift_report_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_schema_drift_report 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.
Report the gap between the app's OpenAPI spec and its V1 API-tests coverage. Reuses the existing schema-coverage endpoint that get_coverage_gaps consumes, but frames the result for V1: which endpoints are uncovered, the recommended order to generate tests for them next (highest-fan-in first), and the count gap. V1 covers the "spec-vs-tests" half of drift. The deeper "spec-vs-actual-handler-behavior" half (run the live app, diff responses against the OpenAPI spec) is a V2 lift — defer until V1 telemetry shows it would unblock real dev journeys.. 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_schema_drift_report: 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_schema_drift_report 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_schema_drift_report 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_schema_drift_report. 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_schema_drift_report 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.