remove_member
Remove a member (accepted or pending) from this project by their member ID or email. Owner only.
This record as markdown: /tools/dev-echorelay-management/remove-member.md
What remove_member does on EchoRelay
AI agents call remove_member to permanently remove resources in EchoRelay, 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 (alternative to memberId — removes the first matching member). |
memberId | string | — | Member record UUID (from list_members). |
Parameters from the server's own tool schema.
Why remove_member is rated Critical
Removing a member is an irreversible action that revokes their access to the project. There is no indication of an undo or soft-delete mechanism. Misuse by an AI agent could lock legitimate users out of a project, making this a high-severity destructive action.
From the tool's definition 'Remove a member (accepted or pending) from this project by their member ID or email'
Attacks that exploit this kind of access
The rule that runs remove_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 remove_member, this is the rule to start with:
remove_member 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 EchoRelay, apply this rule, and every remove_member call is checked against it from then on.
Questions about remove_member
Remove a member (accepted or pending) from this project by their member ID or email. Owner only. It is categorised as a Destructive tool in the EchoRelay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_member 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 remove_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.
remove_member 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 remove_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 remove_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.
remove_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.
Across the catalogue