guest_accept
Accept an invitation SOMEONE ELSE sent YOU, gaining access to their machines. You are the guest here: after this you can use the host's shared infra. Use the 6-character invite code they shared with you. Optionally scope the grant to specific machines so you only take access to the ones you actua...
This record as markdown: /tools/io-github-kivanccakmak-yaver/guest-accept.md
What guest_accept does on Yaver
AI agents call guest_accept 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 |
|---|---|---|---|
code | string | Yes | The 6-character invite code the host shared with you. |
machines | array | — | Optional host device ids to scope your grant to specific machines. Empty = every machine the host offered. |
Parameters from the server's own tool schema.
Why guest_accept is rated Low
Even though guest_accept only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs guest_accept 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_accept, this is the rule to start with:
guest_accept 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_accept call is checked against it from then on.
Questions about guest_accept
Accept an invitation SOMEONE ELSE sent YOU, gaining access to their machines. You are the guest here: after this you can use the host's shared infra. Use the 6-character invite code they shared with you. Optionally scope the grant to specific machines so you only take access to the ones you actually need. To undo it later, use guest_leave. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
guest_accept accepts 2 parameters: code, machines. Required: code. 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_accept: 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_accept 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_accept 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_accept. 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_accept 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