yaver_auth_status
Report Yaver's own sign-in state on this machine: whether a valid Apple/GitHub/Google/Microsoft/email-password Yaver token is present, which user it belongs to, and whether the environment looks headless. Safe to call before signing in.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-status.md
What yaver_auth_status does on Yaver
AI agents call yaver_auth_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why yaver_auth_status is rated Low
This tool reads and reports authentication state without modifying any data, triggering operations, or causing side effects. It is a diagnostic query that an AI agent can safely call to determine current authentication status. The low severity reflects minimal blast radius—misuse would only expose local authentication metadata, not enable unauthorized access or cause harm.
From the tool's definition Tool 'yaver_auth_status' performs a query-only check of 'sign-in state', 'token presence', 'user identity', and 'environment type'. Language indicates pure information retrieval: 'Report', 'whether', 'which user'.
Attacks that exploit this kind of access
The rule that runs yaver_auth_status 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_status, this is the rule to start with:
yaver_auth_status is read-only, so it stays allowed. 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 yaver_auth_status call is checked against it from then on.
Questions about yaver_auth_status
Report Yaver's own sign-in state on this machine: whether a valid Apple/GitHub/Google/Microsoft/email-password Yaver token is present, which user it belongs to, and whether the environment looks headless. Safe to call before signing in. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for yaver_auth_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the yaver_auth_status 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_status. 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_status 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