This record as markdown: /tools/instantkom-mcp-server/remove-team-member.md
What remove_team_member does on instantKOM MCP Server
AI agents call remove_team_member to permanently remove resources in instantKOM MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_team_member is rated Critical
Removing a team member is a destructive action that permanently alters access control and cannot be trivially reversed. While not involving financial transactions or data deletion per se, it represents an irreversible change to organizational structure and user permissions.
From the tool's definition Tool name 'remove_team_member' combined with description 'Remove a team member' indicates irreversible deletion or removal of a user from a team.
Attacks that exploit this kind of access
The rule that runs remove_team_member safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_team_member, this is the rule to start with:
remove_team_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 instantKOM MCP Server, apply this rule, and every remove_team_member call is checked against it from then on.
Questions about remove_team_member
Remove a team member. It is categorised as a Destructive tool in the instantKOM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for remove_team_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 instantKOM MCP Server. Nothing to install.
remove_team_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_team_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_team_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_team_member is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue