Add a git repository to the docs directory with optional sparse checkout. Please do not use
AI agents use add_git_repository to create or update resources in MCP Docs RAG Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Docs RAG Server environment.
This is a Write operation because it creates new data (clones/adds a git repository into the docs directory), which is reversible (the repository can be removed). It does not execute arbitrary code or delete data irreversibly.
From the tool's definition The tool name "add_git_repository" combined with description "Add a git repository to the docs directory" indicates it creates or modifies the local file system by adding repository data.
Documented attack patterns abuse exactly the kind of access add_git_repository gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Docs RAG Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_git_repository:
{
"version": "1",
"default": "deny",
"tools": {
"add_git_repository": {
"limits": [
{
"counter": "add_git_repository_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_git_repository stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a git repository to the docs directory with optional sparse checkout. Please do not use. It is categorised as a Write tool in the MCP Docs RAG Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Docs RAG Server MCP server in PolicyLayer and add a rule for add_git_repository: 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 MCP Docs RAG Server. Nothing to install.
add_git_repository 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 add_git_repository 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 add_git_repository. 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.
add_git_repository is provided by the MCP Docs RAG Server MCP server (kazuph/mcp-docs-rag). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Docs RAG Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MCP Docs RAG Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.