delete_team_member_by_id

Delete a team member by ID via Public API

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_team_member_by_id

What does the delete_team_member_by_id tool do? +

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.

How do I enforce a policy on delete_team_member_by_id? +

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.

What risk level is delete_team_member_by_id? +

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.

Can I rate-limit delete_team_member_by_id? +

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.

How do I block delete_team_member_by_id completely? +

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.

What MCP server provides delete_team_member_by_id? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of instantKOM MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.