guest_revoke
Remove SOMEONE ELSE'S access to YOUR machines. You are the host here: this kicks a guest out of your own shared infra, removing both their pending invitation and their active access. Do NOT use this to give up your own access to a machine someone shared with you — that is guest_leave.
This record as markdown: /tools/io-github-kivanccakmak-yaver/guest-revoke.md
What guest_revoke does on Yaver
AI agents call guest_revoke to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Email address of the guest to remove |
Parameters from the server's own tool schema.
Why guest_revoke is rated Critical
This tool irreversibly revokes access for another user — eliminating both pending invitations and active sessions. Access revocation is not easily undone (the guest would need to be re-invited), making this Destructive. The blast radius is high because misuse could lock legitimate users out of shared infrastructure, disrupting workflows or deployments.
From the tool's definition Remove SOMEONE ELSE'S access to YOUR machines... this kicks a guest out of your own shared infra, removing both their pending invitation and their active access
Attacks that exploit this kind of access
The rule that runs guest_revoke 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_revoke, this is the rule to start with:
guest_revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every guest_revoke call is checked against it from then on.
Questions about guest_revoke
Remove SOMEONE ELSE'S access to YOUR machines. You are the host here: this kicks a guest out of your own shared infra, removing both their pending invitation and their active access. Do NOT use this to give up your own access to a machine someone shared with you — that is guest_leave. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
guest_revoke accepts 1 parameter: email. Required: email. 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_revoke: 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_revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the guest_revoke 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_revoke. 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_revoke 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.
Across the catalogue