oauth_user_create
Create a new OAuth user with a scrypt-hashed password.
This record as markdown: /tools/io-github-kivanccakmak-yaver/oauth-user-create.md
What oauth_user_create does on Yaver
AI agents use oauth_user_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
email | string | Yes | |
password | string | Yes |
Parameters from the server's own tool schema.
Why oauth_user_create is rated Medium
This tool creates new user accounts in an OAuth system, which is a write operation that modifies authentication state. While account creation is theoretically reversible (accounts can be deleted), the primary action is data creation. It is not Destructive because creation itself is not irreversible in the strict sense, and it is not Financial.
From the tool's definition Tool name 'oauth_user_create' and description 'Create a new OAuth user with a scrypt-hashed password' indicate irreversible creation of a new authentication identity.
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs oauth_user_create 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_create, this is the rule to start with:
oauth_user_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 oauth_user_create call is checked against it from then on.
Questions about oauth_user_create
Create a new OAuth user with a scrypt-hashed password. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
oauth_user_create accepts 3 parameters: name, email, password. Required: email, password. 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 oauth_user_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the oauth_user_create 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_create. 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_create 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