yaver_auth_logout
Clear the saved Yaver auth token from ~/.yaver/config.json on this machine. Daemon is left running — call agent_shutdown separately if you want to stop it.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-logout.md
What yaver_auth_logout does on Yaver
AI agents call yaver_auth_logout 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.
Why yaver_auth_logout is rated Critical
This tool irreversibly removes the saved authentication token from the config file. While the daemon continues running, the token deletion cannot be undone (a new login would be required to restore access). This is a destructive modification of a credential store, not a simple write, as it permanently removes authentication state.
From the tool's definition Clear the saved Yaver auth token from ~/.yaver/config.json on this machine
Attacks that exploit this kind of access
The rule that runs yaver_auth_logout 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_logout, this is the rule to start with:
yaver_auth_logout 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_logout call is checked against it from then on.
Questions about yaver_auth_logout
Clear the saved Yaver auth token from ~/.yaver/config.json on this machine. Daemon is left running — call agent_shutdown separately if you want to stop it. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for yaver_auth_logout: 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_logout 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_logout 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_logout. 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_logout 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