auth_oauth_list

List all OAuth providers with their configuration status.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-oauth-list.md

WHAT IT DOES

What auth_oauth_list does on Yaver

AI agents call auth_oauth_list 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.

RISK

Why auth_oauth_list is rated Low

The tool retrieves configuration metadata about OAuth providers without creating, modifying, or deleting any data. This is a pure read operation. Severity is low because listing OAuth configuration is informational and carries minimal risk unless the sensitive credentials themselves were exposed (which the description does not indicate — it only lists provider configuration status).

From the tool's definition Tool description states 'List all OAuth providers' — a querying/enumeration action with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

auth_oauth_list Allowed

auth_oauth_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "auth_oauth_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about auth_oauth_list

What does the auth_oauth_list tool do? +

List all OAuth providers with their configuration status. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on auth_oauth_list? +

Register the Yaver MCP server in PolicyLayer and add a rule for auth_oauth_list: 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 auth_oauth_list? +

auth_oauth_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit auth_oauth_list? +

Yes. Add a rate_limit block to the auth_oauth_list 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 auth_oauth_list completely? +

Set action: deny in the PolicyLayer policy for auth_oauth_list. 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 auth_oauth_list? +

auth_oauth_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →