git_oauth_start

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What git_oauth_start does on Yaver

AI agents use git_oauth_start 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	—	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.

RISK

Why git_oauth_start is rated Medium

This tool initiates an OAuth Device Flow and writes persistent OAuth credentials (access tokens) to local storage and a vault. While it doesn't execute code or delete data, it creates/writes sensitive authentication tokens that could grant broad access to GitHub/GitLab repositories.

From the tool's definition persists the resulting OAuth access token to ~/.yaver/git-credentials.json, provider metadata, and the local vault for CI/deploy use

Risk signalsAccepts URL/endpoint input (host)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_oauth_start 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_oauth_start, this is the rule to start with:

git_oauth_start Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_oauth_start": {
      "limits": [
        {
          "counter": "git_oauth_start_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about git_oauth_start

What does the git_oauth_start tool do? +

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, and the local vault for CI/deploy use, 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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does git_oauth_start accept? +

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.

How do I enforce a policy on git_oauth_start? +

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.

What risk level is git_oauth_start? +

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

Can I rate-limit git_oauth_start? +

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.

How do I block git_oauth_start completely? +

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.

What MCP server provides git_oauth_start? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →