remove_workspace_member
Remove a user from a workspace and revoke workspace access. This does not delete the user from the organization; use delete_user for full removal.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/remove-workspace-member.md
What remove_workspace_member does on Portkey Admin
AI agents call remove_workspace_member to permanently remove resources in Portkey Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_workspace_member is rated Critical
This tool revokes access rights and removes a user from a workspace, which is an irreversible action affecting a user's permissions and workspace membership. While not deleting the user entirely from the organization, it permanently terminates their access to workspace resources. This fits Destructive (irreversible removal of access/data association) rather than Write (reversible modification).
From the tool's definition 'Remove a user from a workspace and revoke workspace access' — this irreversibly removes a user's access to a workspace resource.
Attacks that exploit this kind of access
The rule that runs remove_workspace_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_workspace_member, this is the rule to start with:
remove_workspace_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 Portkey Admin, apply this rule, and every remove_workspace_member call is checked against it from then on.
Questions about remove_workspace_member
Remove a user from a workspace and revoke workspace access. This does not delete the user from the organization; use delete_user for full removal. It is categorised as a Destructive tool in the Portkey Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for remove_workspace_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 Portkey Admin. Nothing to install.
remove_workspace_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_workspace_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_workspace_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_workspace_member is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
Across the catalogue