Add a new remote repository reference. Creates a connection to a remote repository with a name and URL, allowing fetching and pushing changes to and from that repository.
AI agents use git_remote_add to create or update resources in Git MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git MCP Server environment.
git_remote_add modifies repository configuration by adding a remote reference, which is a reversible write operation. While it doesn't directly alter code or data, it configures repository connections. Severity is medium because a malicious remote could enable subsequent data exfiltration or malicious pushes, but the immediate effect is limited to configuration.
From the tool's definition Tool description states it 'Creates a connection to a remote repository with a name and URL', and the sibling tools (git_add, git_commit, git_branch_create, git_checkout) indicate this is a Git management server where configuration changes are reversible…
Attacks that exploit this kind of access
Add a new remote repository reference. Creates a connection to a remote repository with a name and URL, allowing fetching and pushing changes to and from that repository. It is categorised as a Write tool in the Git MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Git MCP Server MCP server in PolicyLayer and add a rule for git_remote_add: 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 Git MCP Server. Nothing to install.
git_remote_add 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 git_remote_add 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 git_remote_add. 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.
git_remote_add is provided by the Git MCP Server MCP server (wty0512/git-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →