invite_member
Invite a person by email to collaborate on this project. Returns the new invitation record; the invitee receives an email with an accept link. Enforces the seat cap for the plan tier. Owner only.
This record as markdown: /tools/dev-echorelay-management/invite-member.md
What invite_member does on EchoRelay
AI agents use invite_member to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
role | string | Yes | Role to assign on acceptance. |
email | string | Yes | Email address to invite. |
Parameters from the server's own tool schema.
Why invite_member is rated Medium
The tool creates (writes) a new invitation record and triggers an email notification. This is reversible—invitations can typically be revoked or expire. It does not delete data (not Destructive), does not move money (not Financial), and does not execute arbitrary code (not Execute).
From the tool's definition Tool creates a new invitation record and sends an email to invitee. Description explicitly states 'Invite a person by email to collaborate' and 'Returns the new invitation record', indicating reversible creation of collaboration state.
Attacks that exploit this kind of access
The rule that runs invite_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EchoRelay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invite_member, this is the rule to start with:
invite_member 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 EchoRelay, apply this rule, and every invite_member call is checked against it from then on.
Questions about invite_member
Invite a person by email to collaborate on this project. Returns the new invitation record; the invitee receives an email with an accept link. Enforces the seat cap for the plan tier. Owner only. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
invite_member accepts 2 parameters: role, email. Required: role, email. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay MCP server in PolicyLayer and add a rule for invite_member: 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 EchoRelay. Nothing to install.
invite_member 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_member 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_member. 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_member is provided by the EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EchoRelay, and thousands of servers like it.
This server
Across the catalogue