This record as markdown: /tools/0xshariq-github-mcp-server/git-remote-add.md
What git_remote_add does on GitHub MCP Server
AI agents use git_remote_add to create or update resources in GitHub MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.
Why git_remote_add is rated Medium
This tool creates a new remote reference in a Git repository, modifying repository configuration. While reversible via git_remote_remove, it represents a Write operation that alters repository state. Severity is medium because misconfiguration could disrupt collaboration workflows, but it doesn't execute code, delete data, or cause financial impact.
From the tool's definition Tool name 'git_remote_add' and description 'Adds a remote repository' indicate creation/modification of Git configuration.
Attacks that exploit this kind of access
The rule that runs git_remote_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_remote_add, this is the rule to start with:
git_remote_add 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub MCP Server, apply this rule, and every git_remote_add call is checked against it from then on.
Questions about git_remote_add
Adds a remote repository. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub 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 GitHub 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 GitHub MCP Server MCP server (0xshariq/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub MCP Server, and thousands of servers like it.
This server
Across the catalogue