git_member_invite
Invite a collaborator to a GitHub or GitLab repo using the neutral forge seam, and report whether the call used CLI transport or direct REST.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-member-invite.md
What git_member_invite does on Yaver
AI agents use git_member_invite to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | — | Forge host override. |
kind | string | — | github or gitlab when the host is ambiguous. |
repo | string | — | Repo slug (`owner/repo`, `group/subgroup/project`) or full clone URL. |
role | string | — | read, triage, write, maintain, or admin. Default: write. |
user | string | Yes | GitHub username, GitLab username, or email (GitLab only). |
directory | string | — | Repo directory; used when repo is omitted. |
Parameters from the server's own tool schema.
Why git_member_invite is rated Medium
This tool creates a new repository collaborator invitation, which is a reversible modification of repository state and access permissions. It does not execute arbitrary code, delete data, or move money. While it does grant access privileges, the core action is creating/modifying an invitation record rather than permanent deletion or financial transaction.
From the tool's definition Tool description states 'Invite a collaborator to a GitHub or GitLab repo', which creates a new collaboration relationship (reversible write operation).
Risk signalsAccepts file system path (directory) · Accepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs git_member_invite 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_member_invite, this is the rule to start with:
git_member_invite 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 Yaver, apply this rule, and every git_member_invite call is checked against it from then on.
Questions about git_member_invite
Invite a collaborator to a GitHub or GitLab repo using the neutral forge seam, and report whether the call used CLI transport or direct REST. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
git_member_invite accepts 6 parameters: host, kind, repo, role, user, directory. Required: user. 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_member_invite: 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_member_invite 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_member_invite 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_member_invite. 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_member_invite 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