Remove a member from a project.
AI agents call plane-project-member-remove to permanently remove resources in Plane — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a project member is a destructive action that revokes access and deletes the membership association. While the member could theoretically be re-added, the action itself is a deletion/removal operation with significant access-control impact, warranting high severity due to potential disruption to project collaboration.
From the tool's definition 'Remove a member from a project' — removal of a member is irreversible in the sense that access is revoked and the membership record is deleted; it cannot be automatically undone.
Attacks that exploit this kind of access
Remove a member from a project. It is categorised as a Destructive tool in the Plane MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Plane MCP server in PolicyLayer and add a rule for plane-project-member-remove: 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 Plane. Nothing to install.
plane-project-member-remove 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 plane-project-member-remove 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 plane-project-member-remove. 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.
plane-project-member-remove is provided by the Plane MCP server (philipvanlewis/plane-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →