yaver_auth_factory_reset
Reset local Yaver auth state on this machine, then restart sign-in from the canonical hosted backend. Useful when browser OAuth succeeded but the local agent kept validating against stale auth state or an old backend.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-factory-reset.md
What yaver_auth_factory_reset does on Yaver
AI agents call yaver_auth_factory_reset to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
headless | boolean | — | Use device-code auth after reset instead of browser auth. |
Parameters from the server's own tool schema.
Why yaver_auth_factory_reset is rated Critical
The tool irreversibly resets local authentication state, which cannot be undone. This destroys existing auth tokens/session data and forces re-authentication. Misuse could lock an AI agent out of the system or disrupt active sessions, making it Destructive in nature with high severity due to the potential to break ongoing authenticated workflows.
From the tool's definition Reset local Yaver auth state on this machine
Attacks that exploit this kind of access
The rule that runs yaver_auth_factory_reset 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 yaver_auth_factory_reset, this is the rule to start with:
yaver_auth_factory_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every yaver_auth_factory_reset call is checked against it from then on.
Questions about yaver_auth_factory_reset
Reset local Yaver auth state on this machine, then restart sign-in from the canonical hosted backend. Useful when browser OAuth succeeded but the local agent kept validating against stale auth state or an old backend. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
yaver_auth_factory_reset accepts 1 parameter: headless. 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 yaver_auth_factory_reset: 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.
yaver_auth_factory_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the yaver_auth_factory_reset 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 yaver_auth_factory_reset. 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.
yaver_auth_factory_reset 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.
Across the catalogue