New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

oauth_user_create

Create a new OAuth user with a scrypt-hashed password.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about oauth_user_create

What does the oauth_user_create tool do? +

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.

What parameters does oauth_user_create accept? +

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.

How do I enforce a policy on oauth_user_create? +

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.

What risk level is oauth_user_create? +

oauth_user_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit oauth_user_create? +

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.

How do I block oauth_user_create completely? +

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.

What MCP server provides oauth_user_create? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.