git_remote_set_url

Changes the URL of an existing remote repository

SERVERGitHub MCP Server SOURCE0xshariq/github-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xshariq-github-mcp-server/git-remote-set-url.md

What git_remote_set_url does on GitHub MCP Server

AI agents use git_remote_set_url 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_set_url is rated Medium

This tool modifies Git remote configuration (a reversible write operation) but carries high severity because changing a remote URL can redirect subsequent git push/pull operations to an attacker-controlled repository, enabling credential theft or malicious code injection. An AI agent tricked into calling this could compromise repository integrity and developer credentials.

From the tool's definition Tool name 'git_remote_set_url' and description 'Changes the URL of an existing remote repository' indicate modification of repository configuration.

Questions about git_remote_set_url

What does the git_remote_set_url tool do? +

Changes the URL of an existing 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.

How do I enforce a policy on git_remote_set_url? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_remote_set_url: 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.

What risk level is git_remote_set_url? +

git_remote_set_url is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit git_remote_set_url? +

Yes. Add a rate_limit block to the git_remote_set_url 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.

How do I block git_remote_set_url completely? +

Set action: deny in the PolicyLayer policy for git_remote_set_url. 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.

What MCP server provides git_remote_set_url? +

git_remote_set_url 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of GitHub MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.