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.
AI agents call git_oauth_status to retrieve information from Yaver without modifying anything — 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.
Even though git_oauth_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
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.