Generate the agent-discovery files that let dev #2 onboard via their AI agent without a human pointing at docs. The doc-stated "loop closure" step. Emits THREE files (the AI writes them with its Write tool): * .claude/skills/keploy/SKILL.md — Claude Code skill. Has YAML frontmatter with a descrip...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Keploy server.
Free to start. No card required.
AI agents use devloop_install_repo_artifacts to create or modify resources in Keploy. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call devloop_install_repo_artifacts repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Keploy.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"devloop_install_repo_artifacts": {
"limits": [
{
"counter": "devloop_install_repo_artifacts_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Keploy policy for all 103 tools.
These attack patterns abuse exactly the kind of access devloop_install_repo_artifacts gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Generate the agent-discovery files that let dev #2 onboard via their AI agent without a human pointing at docs. The doc-stated "loop closure" step. Emits THREE files (the AI writes them with its Write tool): * .claude/skills/keploy/SKILL.md — Claude Code skill. Has YAML frontmatter with a description: that triggers the skill semantically when the dev mentions Keploy / sandbox tests / mocks / api-tests / etc. Body describes the on-disk layout + how to drive Keploy via the MCP. Lazy-loaded — only burns context when the matcher fires. * .cursor/rules/keploy.md — Cursor MDC equivalent for Cursor users (Cursor doesn't read .claude/skills/). * CLAUDE.md — a tiny 3-line POINTER that says "Keploy is configured here; see .claude/skills/keploy/SKILL.md for details." Caters to editors that don't yet understand skills but DO read CLAUDE.md. Idempotent. Re-running this tool against the same repo replaces the Keploy skill body in-place (overwrite-safe — we own the file entirely; the user is not expected to hand-edit it). The pointer in CLAUDE.md uses upsert semantics — only the Keploy line is touched; everything else in the file is preserved. Returns the file paths + content + per-file action. The AI uses its Write tool per the action field.. It is categorised as a Write tool in the Keploy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keploy MCP server in PolicyLayer and add a rule for devloop_install_repo_artifacts: 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_install_repo_artifacts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the devloop_install_repo_artifacts 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_install_repo_artifacts. 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_install_repo_artifacts 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.