set_member_role
Change a member's role between editor, viewer, and billing. Identify the member by their member ID or email (from list_members); the project owner's own role cannot be changed. Returns the updated member record. Owner only.
This record as markdown: /tools/dev-echorelay-management/set-member-role.md
What set_member_role does on EchoRelay
AI agents use set_member_role 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 | The new role. |
email | string | — | Email address (alternative to memberId — targets the first matching member). |
memberId | string | — | Member record UUID (from list_members). |
Parameters from the server's own tool schema.
Why set_member_role is rated Medium
This tool creates or modifies data (member role assignments) in a reversible manner. While it affects permissions and could have downstream consequences, the action itself is a metadata update that can be undone by changing the role again. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or trigger external operations (Execute).
From the tool's definition Tool description explicitly states it "Change[s] a member's role" and "Returns the updated member record." This modifies access control metadata reversibly. The description also notes "Owner only" access restriction.
Attacks that exploit this kind of access
The rule that runs set_member_role 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 set_member_role, this is the rule to start with:
set_member_role 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 set_member_role call is checked against it from then on.
Questions about set_member_role
Change a member's role between editor, viewer, and billing. Identify the member by their member ID or email (from list_members); the project owner's own role cannot be changed. Returns the updated member record. 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.
set_member_role accepts 3 parameters: role, email, memberId. Required: role. 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 set_member_role: 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.
set_member_role 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 set_member_role 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 set_member_role. 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.
set_member_role 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