This record as markdown: /tools/io-github-kivanccakmak-yaver/auth-oauth-save.md
What auth_oauth_save does on Yaver
AI agents use auth_oauth_save 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 |
|---|---|---|---|
provider | string | Yes | |
credentials | object | Yes | Key-value pairs (e.g. GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET) |
Parameters from the server's own tool schema.
Why auth_oauth_save is rated Medium
This tool writes sensitive OAuth credentials to a local environment file. While not destructive (reversible) or financial, it is a Write operation that modifies configuration state. The severity is high because misconfigured or compromised OAuth credentials can lead to account takeover, unauthorized API access, and exposure of sensitive application secrets.
From the tool's definition Saves OAuth credentials to .env.local - creates or modifies environment configuration files with sensitive authentication data.
Risk signalsHandles credentials or secrets (credentials)
Attacks that exploit this kind of access
The rule that runs auth_oauth_save 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_save, this is the rule to start with:
auth_oauth_save 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 auth_oauth_save call is checked against it from then on.
Questions about auth_oauth_save
Save OAuth credentials to .env.local. 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.
auth_oauth_save accepts 2 parameters: provider, credentials. Required: provider, credentials. 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 auth_oauth_save: 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.
auth_oauth_save 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 auth_oauth_save 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 auth_oauth_save. 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.
auth_oauth_save 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