switch_cost

Estimate monthly cost across all switch targets based on current project usage.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/switch-cost.md

WHAT IT DOES

What switch_cost does on Yaver

AI agents call switch_cost 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
`directory`	string	—

Parameters from the server's own tool schema.

RISK

Why switch_cost is rated Low

The tool estimates/calculates cost information based on existing usage data. It is a read/query operation that retrieves and computes cost projections without making any changes, executing code, or committing financial obligations.

From the tool's definition Estimate monthly cost across all switch targets based on current project usage

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

switch_cost Allowed

switch_cost 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": {
    "switch_cost": {}
  }
}

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

FAQ

Questions about switch_cost

What does the switch_cost tool do? +

Estimate monthly cost across all switch targets based on current project usage. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does switch_cost accept? +

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

How do I enforce a policy on switch_cost? +

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

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

Can I rate-limit switch_cost? +

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

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

switch_cost 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

The MCP Attack Database →

Guides

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