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.

Server Portkey Admin CodesWhat/portkey-admin-mcp
Category Destructive
Risk class Critical
Parameters 22 required

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.

ParameterTypeRequiredDescription
user_id string Yes The user ID to remove
workspace_id string Yes The workspace ID

Parameters from the server's own tool schema.

Why remove_workspace_member needs a policy

An AI agent that decides to call remove_workspace_member doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Portkey Admin is gone — there is no undo for destructive operations.

Questions about remove_workspace_member

What does the remove_workspace_member tool do? +

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.

What parameters does remove_workspace_member accept? +

remove_workspace_member accepts 2 parameters: user_id, workspace_id. Required: user_id, workspace_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_workspace_member? +

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.

What risk level is remove_workspace_member? +

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.

Can I rate-limit remove_workspace_member? +

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.

How do I block remove_workspace_member completely? +

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.

What MCP server provides remove_workspace_member? +

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.