delete_team_member_by_id
Delete a team member by ID via Public API
This record as markdown: /tools/instantkom-mcp-server/delete-team-member-by-id.md
What delete_team_member_by_id does on instantKOM MCP Server
AI agents call delete_team_member_by_id 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 delete_team_member_by_id is rated Critical
Deletion of team members is a destructive action that cannot be reversed without manual intervention (e.g., re-adding the member). An AI agent with access to this tool could maliciously remove legitimate team members, disrupt operations, or cause data loss. This is more severe than Write (which is reversible) and warrants high severity due to potential operational impact.
From the tool's definition Tool name contains 'delete' and description states 'Delete a team member by ID' — this irreversibly removes a user account or team membership with no undo mechanism.
Attacks that exploit this kind of access
The rule that runs delete_team_member_by_id 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 delete_team_member_by_id, this is the rule to start with:
delete_team_member_by_id 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 delete_team_member_by_id call is checked against it from then on.
Questions about delete_team_member_by_id
Delete a team member by ID via Public API. 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 delete_team_member_by_id: 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.
delete_team_member_by_id 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 delete_team_member_by_id 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 delete_team_member_by_id. 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.
delete_team_member_by_id 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