git_remotes

List remotes.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/git-remotes.md

WHAT IT DOES

What git_remotes does on Yaver

AI agents call git_remotes to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why git_remotes is rated Low

This tool performs a read-only operation (listing git remotes) with no side effects. It retrieves and returns configuration data without altering state, executing code, or triggering external operations. The low severity reflects minimal blast radius if misused by an agent.

From the tool's definition Tool name is 'git_remotes' and description states 'List remotes' — a query operation that retrieves git remote configuration without modification or execution.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_remotes safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_remotes, this is the rule to start with:

git_remotes Allowed

git_remotes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_remotes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_remotes call is checked against it from then on.

FAQ

Questions about git_remotes

What does the git_remotes tool do? +

List remotes. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does git_remotes accept? +

git_remotes accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on git_remotes? +

Register the Yaver MCP server in PolicyLayer and add a rule for git_remotes: 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 Yaver. Nothing to install.

What risk level is git_remotes? +

git_remotes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_remotes? +

Yes. Add a rate_limit block to the git_remotes 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_remotes completely? +

Set action: deny in the PolicyLayer policy for git_remotes. 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_remotes? +

git_remotes is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →