yaver_billing_status

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-billing-status.md

WHAT IT DOES

What yaver_billing_status does on Yaver

AI agents call yaver_billing_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.

RISK

Why yaver_billing_status is rated Low

This tool performs a pure information retrieval operation on billing metadata. It queries plan status, remaining active hours, and feature flags—all read operations with no side effects. While it touches billing-related data, it does not perform financial transactions, initiate charges, or modify account state.

From the tool's definition The tool description explicitly states "Check the user's current Yaver plan" and "included Cloud Workspace active-hours left, and managed-inference flag if present." The verb is read-only: it retrieves billing/plan status information without modifying,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs yaver_billing_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_billing_status, this is the rule to start with:

yaver_billing_status Allowed

yaver_billing_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_billing_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every yaver_billing_status call is checked against it from then on.

FAQ

Questions about yaver_billing_status

What does the yaver_billing_status tool do? +

Check the user's current Yaver plan: Free, Relay Pro, or Cloud Workspace; included Cloud Workspace active-hours left, and managed-inference flag if present. Call this first to know if they've already purchased before offering a checkout. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on yaver_billing_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for yaver_billing_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.

What risk level is yaver_billing_status? +

yaver_billing_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit yaver_billing_status? +

Yes. Add a rate_limit block to the yaver_billing_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.

How do I block yaver_billing_status completely? +

Set action: deny in the PolicyLayer policy for yaver_billing_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.

What MCP server provides yaver_billing_status? +

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →