remove_project_member
Remove a project member BY EMAIL. The project owner cannot be removed.
This record as markdown: /tools/a3plus-mcp/remove-project-member.md
What remove_project_member does on A3plus
AI agents call remove_project_member to permanently remove resources in A3plus, 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 | Yes | Email of the member to remove. |
projectId | string | Yes | The A3Plus project ID. |
Parameters from the server's own tool schema.
Why remove_project_member is rated Critical
An AI agent that decides to call remove_project_member doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from A3plus is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remove_project_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_project_member, this is the rule to start with:
remove_project_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 A3plus, apply this rule, and every remove_project_member call is checked against it from then on.
Questions about remove_project_member
Remove a project member BY EMAIL. The project owner cannot be removed. It is categorised as a Destructive tool in the A3plus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_project_member accepts 2 parameters: email, projectId. Required: email, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for remove_project_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 A3plus. Nothing to install.
remove_project_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_project_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_project_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_project_member is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
Across the catalogue