Fetch a git repository into /workspace. Args: repo_url: Repository URL (https or ssh). version: Branch/tag/commit to checkout (None = default branch). target_dir: Optional specific directory; defaults to a name derived from the URL. When provided, it must be inside the container under /workspace;...
AI agents call fetch_repo to retrieve information from Pwno without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads/clones a remote repository and stores it locally in /workspace. While this does write files to the local filesystem, the operation is reversible (files can be deleted) and non-destructive in nature. The core function is data retrieval.
From the tool's definition Tool description states 'Fetch a git repository into /workspace' - this retrieves data from an external source without modifying the source repository or performing destructive operations.
Documented attack patterns abuse exactly the kind of access fetch_repo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_repo:
{
"version": "1",
"default": "deny",
"tools": {
"fetch_repo": {}
}
}fetch_repo is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a git repository into /workspace. Args: repo_url: Repository URL (https or ssh). version: Branch/tag/commit to checkout (None = default branch). target_dir: Optional specific directory; defaults to a name derived from the URL. When provided, it must be inside the container under /workspace; relative paths resolve under /workspace. shallow: Whether to clone shallowly. It is categorised as a Read tool in the Pwno MCP Server, which means it retrieves data without modifying state.
Register the Pwno MCP server in PolicyLayer and add a rule for fetch_repo: 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 Pwno. Nothing to install.
fetch_repo 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 fetch_repo 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 fetch_repo. 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.
fetch_repo is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.