guest_delete
Delete a guest row from YOUR host guest list. This first revokes/cancels any live access, then hides the old invite/access row from normal lists. It is not a block: you can invite the same person again later. Prefer inviteId for exact duplicate-row deletion; email or userId are accepted as fallback.
This record as markdown: /tools/io-github-kivanccakmak-yaver/guest-delete.md
What guest_delete does on Yaver
AI agents call guest_delete 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 | — | Email address of the guest row(s) to delete when inviteId is not known. |
userId | string | — | Public Yaver user id of the guest to delete when inviteId is not known. |
inviteId | string | — | Exact guest invitation id to hide. Best option when duplicate rows exist. |
Parameters from the server's own tool schema.
Why guest_delete is rated Critical
This tool permanently removes access records and revokes live access. Although described as non-blocking (the same person can be invited again), the deletion itself is irreversible and affects authentication/authorization state. The action modifies security-critical data structures (guest list, access rows) in a way that cannot be undone without recreating the record.
From the tool's definition Tool description states 'Delete a guest row' and 'hides the old invite/access row from normal lists' with explicit mention of revocation. The parameters (inviteId, email, userId) enable irreversible removal of access control records.
Attacks that exploit this kind of access
The rule that runs guest_delete 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_delete, this is the rule to start with:
guest_delete 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_delete call is checked against it from then on.
Questions about guest_delete
Delete a guest row from YOUR host guest list. This first revokes/cancels any live access, then hides the old invite/access row from normal lists. It is not a block: you can invite the same person again later. Prefer inviteId for exact duplicate-row deletion; email or userId are accepted as fallback. 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_delete accepts 3 parameters: email, userId, inviteId. 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_delete: 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_delete 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_delete 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_delete. 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_delete 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