yaver_auth_capabilities
Report deployment auth capabilities, including whether owner/test email-password sign-in is currently enabled. Does not accept or expose passwords; raw automation passwords belong in local keychain/.env or GitHub Secrets.
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-auth-capabilities.md
What yaver_auth_capabilities does on Yaver
AI agents call yaver_auth_capabilities 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
convex_url | string | — | Optional override for the Convex backend URL (defaults to the stored or hosted endpoint). |
Parameters from the server's own tool schema.
Why yaver_auth_capabilities is rated Low
This tool retrieves and reports the current state of auth capabilities for a deployment. It performs a query operation with no modifications to data, no code execution, and no destructive effects. The severity is low because knowing auth capabilities poses minimal risk — the tool itself neither stores nor exposes credentials, and querying configuration is a standard read operation.
From the tool's definition Tool name 'yaver_auth_capabilities' and description 'Report deployment auth capabilities' — the verb is 'Report', which is a read operation that queries/retrieves information about authentication configuration.
Attacks that exploit this kind of access
The rule that runs yaver_auth_capabilities 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_capabilities, this is the rule to start with:
yaver_auth_capabilities 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_capabilities call is checked against it from then on.
Questions about yaver_auth_capabilities
Report deployment auth capabilities, including whether owner/test email-password sign-in is currently enabled. Does not accept or expose passwords; raw automation passwords belong in local keychain/.env or GitHub Secrets. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
yaver_auth_capabilities accepts 1 parameter: convex_url. 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_capabilities: 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_capabilities 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_capabilities 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_capabilities. 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_capabilities 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