git_oauth_status
Poll the state of an in-flight GitHub/GitLab Device Flow session started via git_oauth_start. Returns state ∈ {pending, done, error, expired, unknown} plus the username on success. Safe to call repeatedly at the interval the start call returned.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-oauth-status.md
What git_oauth_status does on Yaver
AI agents call git_oauth_status 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 |
|---|---|---|---|
device_id | string | — | Optional remote device ID/alias — checks the session on that peer |
session_id | string | Yes |
Parameters from the server's own tool schema.
Why git_oauth_status is rated Low
git_oauth_status is a read-only polling operation that queries the status of an authentication session. It retrieves information (state, username) without side effects. The tool does not create, modify, delete, execute code, or move money. Misuse would only yield authentication status data, posing low risk even if an agent calls it maliciously.
From the tool's definition Tool description states it 'Poll[s] the state' and 'Returns state' without modifying anything. The operation is explicitly safe to call repeatedly and only retrieves OAuth session status information.
Attacks that exploit this kind of access
The rule that runs git_oauth_status 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_status, this is the rule to start with:
git_oauth_status 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_oauth_status call is checked against it from then on.
Questions about git_oauth_status
Poll the state of an in-flight GitHub/GitLab Device Flow session started via git_oauth_start. Returns state ∈ {pending, done, error, expired, unknown} plus the username on success. Safe to call repeatedly at the interval the start call returned. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_oauth_status accepts 2 parameters: device_id, session_id. Required: session_id. 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_status: 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_status 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_oauth_status 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_status. 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_status 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