happ_company_remove_user
Удаляет участника из компании. Требует роль owner/admin. (DELETE /companies/:id/users/:userId)
This record as markdown: /tools/happ-ai-platform-mcp/happ-company-remove-user.md
What happ_company_remove_user does on Platform
AI agents call happ_company_remove_user to permanently remove resources in Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
userId | string | Yes | ID пользователя |
companyId | string | Yes | ID компании |
Parameters from the server's own tool schema.
Why happ_company_remove_user is rated Critical
An AI agent that decides to call happ_company_remove_user doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Platform is gone. There is no undo for destructive operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs happ_company_remove_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For happ_company_remove_user, this is the rule to start with:
happ_company_remove_user 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 Platform, apply this rule, and every happ_company_remove_user call is checked against it from then on.
Questions about happ_company_remove_user
Удаляет участника из компании. Требует роль owner/admin. (DELETE /companies/:id/users/:userId). It is categorised as a Destructive tool in the Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
happ_company_remove_user accepts 2 parameters: userId, companyId. Required: userId, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_company_remove_user: 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 Platform. Nothing to install.
happ_company_remove_user 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 happ_company_remove_user 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 happ_company_remove_user. 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.
happ_company_remove_user is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Platform, and thousands of servers like it.
Across the catalogue