guest_invite

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/guest-invite.md

WHAT IT DOES

What guest_invite does on Yaver

AI agents use guest_invite to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required	Description
`email`	string	—	Email address of the person to invite. Provide either email or user_id.
`scope`	string	—	Access tier: 'feedback-only' (default, hardened end-user), 'sdk-project' (Feedback SDK style project-scoped access), or 'full' (classic teammate).
`user_id`	string	—	Public Yaver user id of the person to invite. Provide either email or user_id.
`projects`	array	—	Narrow this grant to specific project names/slugs on the host. Empty = all. Useful when feedback-only or sdk-project guests should only see Project A, not B/C.
`device_ids`	array	—	Optional host device ids to pre-scope the invitation to specific machines. Empty = all host machines.

Parameters from the server's own tool schema.

RISK

Why guest_invite is rated Medium

This tool creates invitation records and modifies access control by granting new users access to a machine/system with configurable permission scopes. It is reversible (invitations expire, can presumably be revoked) and does not permanently delete data or move money, making it Write rather than Destructive or Financial.

From the tool's definition Invite a guest by email or Yaver user id to use your machine. Max 5 guests, invitation expires in 2 days. Default scope is 'feedback-only'...Use scope='full' for teammate invites that need task / vibing / dev access, or scope='sdk-project'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs guest_invite 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_invite, this is the rule to start with:

guest_invite Rate-limited

guest_invite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "guest_invite": {
      "limits": [
        {
          "counter": "guest_invite_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every guest_invite call is checked against it from then on.

FAQ

Questions about guest_invite

What does the guest_invite tool do? +

Invite a guest by email or Yaver user id to use your machine. Max 5 guests, invitation expires in 2 days. Default scope is 'feedback-only' — the hardened tier for end-users of your app (no /tasks, no /vibing, no dev-server proxy, no project enumeration; /info is redacted; any fix-triggered task runs inside Docker). Use scope='full' for teammate invites that need task / vibing / dev access, or scope='sdk-project' for Feedback SDK style project-scoped access. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does guest_invite accept? +

guest_invite accepts 5 parameters: email, scope, user_id, projects, device_ids. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on guest_invite? +

Register the Yaver MCP server in PolicyLayer and add a rule for guest_invite: 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.

What risk level is guest_invite? +

guest_invite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit guest_invite? +

Yes. Add a rate_limit block to the guest_invite 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.

How do I block guest_invite completely? +

Set action: deny in the PolicyLayer policy for guest_invite. 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.

What MCP server provides guest_invite? +

guest_invite 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →