invite
Share Yaver with a colleague — copies invite link, opens email, or generates a Slack message.
This record as markdown: /tools/io-github-kivanccakmak-yaver/invite.md
What invite does on Yaver
AI agents use 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 |
|---|---|---|---|
method | string | — | clipboard, email, or slack |
recipient | string | — | Email address (for email method) |
Parameters from the server's own tool schema.
Why invite is rated Medium
This tool composes and initiates outbound communication (email, Slack) to share access to Yaver with colleagues. It creates new invitation artifacts and may modify system state (clipboard, email client). While not destructive or financial, it does create reversible data artifacts and trigger external operations.
From the tool's definition Tool description states it "copies invite link, opens email, or generates a Slack message" — actions that create or modify data (email drafts, message composition, clipboard state) and trigger external communications with side effects.
Attacks that exploit this kind of access
The rule that runs 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 invite, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every invite call is checked against it from then on.
Questions about invite
Share Yaver with a colleague — copies invite link, opens email, or generates a Slack message. 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.
invite accepts 2 parameters: method, recipient. 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 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.
invite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue