When you need to shallow clone a Git repository, optionally limiting to a specific folder and its descendants, then read its system prompt and agent config and run Codex CLI accordingly.
AI agents invoke clone_and_write_prompt to trigger actions in Agentic Developer MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs multiple high-risk actions: it clones an arbitrary external Git repository (potentially malicious code), reads system prompts and agent configs from that repo, and then executes Codex CLI against it.
From the tool's definition 'shallow clone a Git repository', 'run Codex CLI accordingly' — clones external repo and executes Codex CLI against it
Documented attack patterns abuse exactly the kind of access clone_and_write_prompt gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Developer MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for clone_and_write_prompt:
{
"version": "1",
"default": "deny",
"tools": {
"clone_and_write_prompt": {
"limits": [
{
"counter": "clone_and_write_prompt_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}clone_and_write_prompt stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
When you need to shallow clone a Git repository, optionally limiting to a specific folder and its descendants, then read its system prompt and agent config and run Codex CLI accordingly. It is categorised as a Execute tool in the Agentic Developer MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agentic Developer MCP server in PolicyLayer and add a rule for clone_and_write_prompt: 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 Agentic Developer MCP. Nothing to install.
clone_and_write_prompt 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 clone_and_write_prompt 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 clone_and_write_prompt. 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.
clone_and_write_prompt is provided by the Agentic Developer MCP server (teabranch/agentic-developer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Agentic Developer MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Agentic Developer MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.