set_group_kick

Kick member from group

SERVERNapCat MCP Server SOURCE1021143806/napcat_mcp

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/1021143806-napcat-mcp/set-group-kick.md

WHAT IT DOES

What set_group_kick does on NapCat MCP Server

AI agents call set_group_kick to permanently remove resources in NapCat MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why set_group_kick is rated Critical

Kicking a group member is a destructive social/platform action: the removal is immediate and cannot be automatically undone. The ejected user loses group membership and access. This has a high blast radius if misused, as an AI agent could mass-kick members from a group.

From the tool's definition 'Kick member from group' — removing a member from a group is an irreversible action (the member is ejected and must be re-invited to rejoin).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_group_kick safely

PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_group_kick, this is the rule to start with:

set_group_kick Hidden

set_group_kick is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "set_group_kick"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect NapCat MCP Server, apply this rule, and every set_group_kick call is checked against it from then on.

FAQ

Questions about set_group_kick

What does the set_group_kick tool do? +

Kick member from group. It is categorised as a Destructive tool in the NapCat 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 set_group_kick? +

Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for set_group_kick: 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 NapCat MCP Server. Nothing to install.

What risk level is set_group_kick? +

set_group_kick 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 set_group_kick? +

Yes. Add a rate_limit block to the set_group_kick 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 set_group_kick completely? +

Set action: deny in the PolicyLayer policy for set_group_kick. 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 set_group_kick? +

set_group_kick is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on NapCat MCP Server, and thousands of servers like it.

This server

All 57 NapCat MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →