This record as markdown: /tools/io-github-kivanccakmak-yaver/remote-cost.md
What remote_cost does on Yaver
AI agents call remote_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.
Why remote_cost is rated Low
This tool retrieves and displays financial cost information but does not move money, commit financial obligations, or execute transactions. It is a read-only reporting function that queries existing cost data. The 'Show' verb and 'across all remote machines' scope suggest a data retrieval operation with no side effects.
From the tool's definition Tool name 'remote_cost' and description 'Show monthly cost across all remote machines' indicate a query/reporting operation that retrieves cost data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs remote_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 remote_cost, this is the rule to start with:
remote_cost 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 remote_cost call is checked against it from then on.
Questions about remote_cost
Show monthly cost across all remote machines. 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 remote_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.
remote_cost 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 remote_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.
Set action: deny in the PolicyLayer policy for remote_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.
remote_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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue