resend_invite
Re-send the invitation email for a still-pending invite, by member ID or email (from list_members). The original accept link is reused. Already-accepted members are rejected. Owner only.
This record as markdown: /tools/dev-echorelay-management/resend-invite.md
What resend_invite does on EchoRelay
AI agents use resend_invite 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 |
|---|---|---|---|
email | string | — | Email address (alternative to memberId — targets the first matching pending invite). |
memberId | string | — | Member record UUID (from list_members). |
Parameters from the server's own tool schema.
Why resend_invite is rated Medium
This tool sends an email invitation to a pending member, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), handle financial transactions (Financial), or retrieve data without side effects (Read). The 'Owner only' permission indicates proper access control is in place.
From the tool's definition Tool description states 'Re-send the invitation email' and references 'Owner only' permission control. It modifies invite state by resending an existing invitation, creating a side effect (email delivery) that is reversible or inconsequential.
Attacks that exploit this kind of access
The rule that runs resend_invite 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 resend_invite, this is the rule to start with:
resend_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 EchoRelay, apply this rule, and every resend_invite call is checked against it from then on.
Questions about resend_invite
Re-send the invitation email for a still-pending invite, by member ID or email (from list_members). The original accept link is reused. Already-accepted members are rejected. 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.
resend_invite accepts 2 parameters: email, memberId. 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 resend_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 EchoRelay. Nothing to install.
resend_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 resend_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 resend_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.
resend_invite 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