oauth_client_create
Register a new OAuth client. The returned client_secret is only shown once — save it immediately.
This record as markdown: /tools/io-github-kivanccakmak-yaver/oauth-client-create.md
What oauth_client_create does on Yaver
AI agents use oauth_client_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 | Yes | |
scopes | array | — | |
redirectUris | array | Yes |
Parameters from the server's own tool schema.
Why oauth_client_create is rated Medium
This tool creates new OAuth client credentials, which are security-sensitive artifacts. It is reversible (clients can be deleted/revoked), so it falls under Write rather than Destructive. However, the high severity reflects that misuse could expose authentication secrets, grant unauthorized API access, or enable privilege escalation if an AI agent creates clients with excessive scopes or in unintended applications.
From the tool's definition Tool name 'oauth_client_create' and description 'Register a new OAuth client' indicates creation of a new authentication credential artifact.
Attacks that exploit this kind of access
The rule that runs oauth_client_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_client_create, this is the rule to start with:
oauth_client_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_client_create call is checked against it from then on.
Questions about oauth_client_create
Register a new OAuth client. The returned client_secret is only shown once — save it immediately. 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_client_create accepts 3 parameters: name, scopes, redirectUris. Required: name, redirectUris. 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_client_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_client_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_client_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_client_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_client_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