Start a GitHub or GitLab Device Flow (RFC 8628) authorization on the local machine or a remote owned peer. Returns a short user_code + verification_uri the user opens in any browser to approve. The agent polls in the background and persists the resulting OAuth access token to ~/.yaver/git-credent...
AI agents invoke git_oauth_start to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
host | string | — | Defaults to github.com / gitlab.com |
provider | string | Yes | |
device_id | string | — | Optional remote device ID/alias — runs the flow on that peer |
Parameters from the server's own tool schema.
git_oauth_start triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
Start a GitHub or GitLab Device Flow (RFC 8628) authorization on the local machine or a remote owned peer. Returns a short user_code + verification_uri the user opens in any browser to approve. The agent polls in the background and persists the resulting OAuth access token to ~/.yaver/git-credentials.json + provider metadata, exactly like /git/provider/setup. Token never reaches Convex. Poll git_oauth_status to learn when approval completes. Requires a registered Device Flow OAuth Client ID — see error message for setup if not configured. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
git_oauth_start accepts 3 parameters: host, provider, device_id. Required: provider. 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_oauth_start: 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_oauth_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the git_oauth_start 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_oauth_start. 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_oauth_start 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.