Remove a member from an org. Requires an active
AI agents call remove_org_member to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a member from an organization is a destructive, access-altering action. It revokes the member's permissions and access to org resources. While the member could theoretically be re-added, the action itself is not automatically reversible and can have significant blast radius if misused by an AI agent (e.g., removing critical members or administrators).
From the tool's definition 'Remove a member from an org' — removing organizational membership is an irreversible administrative action that revokes access and cannot be easily undone without re-inviting the member.
Attacks that exploit this kind of access
Remove a member from an org. Requires an active. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for remove_org_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 Run402. Nothing to install.
remove_org_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_org_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_org_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_org_member is provided by the Run402 MCP server (kychee-com/run402). 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 →