This record as markdown: /tools/io-github-kivanccakmak-yaver/guest-usage.md
What guest_usage does on Yaver
AI agents call guest_usage 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 |
|---|---|---|---|
date | string | — | Date in YYYY-MM-DD format (default: today) |
Parameters from the server's own tool schema.
Why guest_usage is rated Low
This tool only queries and retrieves guest usage statistics—a passive data retrieval operation with no side effects. It does not create, modify, delete, or execute any actions. The low severity reflects minimal blast radius: misuse would only expose usage metrics, not enable destructive or financial harm.
From the tool's definition Tool name 'guest_usage' and description 'View guest usage stats for today or a specific date' indicate a read-only operation that retrieves historical usage data without modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs guest_usage 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 guest_usage, this is the rule to start with:
guest_usage 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 guest_usage call is checked against it from then on.
Questions about guest_usage
View guest usage stats for today or a specific date. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
guest_usage accepts 1 parameter: date. 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 guest_usage: 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.
guest_usage 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 guest_usage 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 guest_usage. 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.
guest_usage 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