This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-oauth-test.md
What auth_oauth_test does on Yaver
AI agents invoke auth_oauth_test 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 |
|---|---|---|---|
provider | string | Yes |
Parameters from the server's own tool schema.
Why auth_oauth_test is rated High
Testing an OAuth flow end-to-end executes an external authentication process involving real network calls and potentially real credential exchanges. This is not a passive read; it actively initiates and drives an OAuth flow. Severity is medium because misuse could trigger unintended authentication sessions or expose OAuth tokens, but does not directly destroy data or move money.
From the tool's definition 'Test an OAuth flow end-to-end' — triggers an external OAuth authentication flow
Attacks that exploit this kind of access
The rule that runs auth_oauth_test 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 auth_oauth_test, this is the rule to start with:
auth_oauth_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 auth_oauth_test call is checked against it from then on.
Questions about auth_oauth_test
Test an OAuth flow end-to-end. 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.
auth_oauth_test accepts 1 parameter: provider. 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 auth_oauth_test: 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.
auth_oauth_test 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 auth_oauth_test 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 auth_oauth_test. 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.
auth_oauth_test 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.
Across the catalogue