git_members
List who has access to a GitHub or GitLab repo. Resolves explicit repo > directory > cwd and reports whether the call used CLI transport or direct REST.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-members.md
What git_members does on Yaver
AI agents call git_members 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 |
|---|---|---|---|
host | string | — | Forge host override (e.g. ghe.example.com or gitlab.example.com). |
kind | string | — | github or gitlab when the host is ambiguous. |
repo | string | — | Repo slug (`owner/repo`, `group/subgroup/project`) or full clone URL. |
directory | string | — | Repo directory; used when repo is omitted. |
Parameters from the server's own tool schema.
Why git_members is rated Low
This tool retrieves and reports existing access control data from version control platforms. It has no side effects—it does not create, modify, delete, or execute anything. The information returned is typically public or user-authorized metadata about repository permissions.
From the tool's definition Tool name is 'git_members' and description states 'List who has access to a GitHub or GitLab repo.' The verb 'List' indicates a read-only query operation that retrieves membership/access information without modifying any data.
Risk signalsAccepts file system path (directory) · Accepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs git_members 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_members, this is the rule to start with:
git_members is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every git_members call is checked against it from then on.
Questions about git_members
List who has access to a GitHub or GitLab repo. Resolves explicit repo > directory > cwd and reports whether the call used CLI transport or direct REST. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_members accepts 4 parameters: host, kind, repo, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for git_members: 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.
git_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the git_members 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_members. 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_members 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue