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

auth_oauth_save

Save OAuth credentials to .env.local.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 22 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/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.

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

Questions about auth_oauth_save

What does the auth_oauth_save tool do? +

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.

What parameters does auth_oauth_save accept? +

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.

How do I enforce a policy on auth_oauth_save? +

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.

What risk level is auth_oauth_save? +

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

Can I rate-limit auth_oauth_save? +

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.

How do I block auth_oauth_save completely? +

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.

What MCP server provides auth_oauth_save? +

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.

// 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.