oauth_user_list
List registered OAuth users (email + id only, never hashes).
This record as markdown: /tools/io-github-kivanccakmak-yaver/oauth-user-list.md
What oauth_user_list does on Yaver
AI agents call oauth_user_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.
Why oauth_user_list is rated Low
This tool retrieves user information (email and id) without side effects or the ability to modify, delete, or execute operations. It is purely informational. While it does expose PII (email addresses), the risk is limited to information disclosure rather than mutation or destructive capability, justifying a 'low' severity classification for an AI agent misusing it.
From the tool's definition 'List registered OAuth users (email + id only, never hashes)' - the verb 'List' and qualifier 'only' indicate a read-only retrieval of user metadata without modification or deletion.
Attacks that exploit this kind of access
The rule that runs oauth_user_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 oauth_user_list, this is the rule to start with:
oauth_user_list 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 oauth_user_list call is checked against it from then on.
Questions about oauth_user_list
List registered OAuth users (email + id only, never hashes). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for oauth_user_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.
oauth_user_list 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 oauth_user_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.
Set action: deny in the PolicyLayer policy for oauth_user_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.
oauth_user_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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue