yaver_billing_checkout

SERVERYaver SOURCEyaver-cli

Critical RISK CLASS

Category Financial

Parameters 10 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What yaver_billing_checkout does on Yaver

AI agents use yaver_billing_checkout to commit financial operations through Yaver, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`plan`	string	—	"relay" ($9/mo Relay Pro) or "workspace" ($29/mo Cloud Workspace). Default: relay.

Parameters from the server's own tool schema.

RISK

Why yaver_billing_checkout is rated Critical

This tool initiates a financial transaction by generating a payment/checkout link for paid subscription plans. Even though it only produces a link (not completing the payment directly), it is explicitly designed to commit the user to recurring financial obligations ($9/mo or $29/mo). This falls squarely in the Financial category.

From the tool's definition 'Get a payment link to subscribe to a Yaver plan' with plans at '$9/mo' and '$29/mo' — commits financial obligations via subscription purchase

Attacks that exploit this kind of access

RECOMMENDED RULE

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

yaver_billing_checkout Approval-gated

Any call to yaver_billing_checkout is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "yaver_billing_checkout": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE 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_checkout call is checked against it from then on.

FAQ

Questions about yaver_billing_checkout

What does the yaver_billing_checkout tool do? +

Get a payment link to subscribe to a Yaver plan. plan="relay" = Relay Pro ($9/mo private relay). plan="workspace" = Cloud Workspace ($29/mo saved cloud workspace, Relay Pro included, BYO Claude/Codex/OpenCode). The buyer MUST pay with the same email they signed into Yaver with. Call yaver_billing_status first to avoid offering a plan they already have. It is categorised as a Financial tool in the Yaver MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does yaver_billing_checkout accept? +

yaver_billing_checkout accepts 1 parameter: plan. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on yaver_billing_checkout? +

Register the Yaver MCP server in PolicyLayer and add a rule for yaver_billing_checkout: 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_checkout? +

yaver_billing_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit yaver_billing_checkout? +

Yes. Add a rate_limit block to the yaver_billing_checkout 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_checkout completely? +

Set action: deny in the PolicyLayer policy for yaver_billing_checkout. 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_checkout? +

yaver_billing_checkout 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →