set_group_ban

Mute group member

SERVERNapCat MCP Server SOURCE1021143806/napcat_mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1021143806-napcat-mcp/set-group-ban.md

WHAT IT DOES

What set_group_ban does on NapCat MCP Server

AI agents invoke set_group_ban to trigger actions in NapCat MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why set_group_ban is rated High

This tool executes an action on an external platform (QQ group) that restricts a member's ability to send messages. While it may be reversible (bans can typically be lifted), the primary action is executing an operation with significant social impact. It falls under Execute as it triggers an external operation whose effects depend on arguments (target user, duration).

From the tool's definition 'set_group_ban' - 'Mute group member': triggers an external operation (muting a user in a QQ group) that affects another user's ability to communicate

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_group_ban 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_ban, this is the rule to start with:

set_group_ban Rate-limited

set_group_ban stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_group_ban": {
      "limits": [
        {
          "counter": "set_group_ban_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_ban call is checked against it from then on.

FAQ

Questions about set_group_ban

What does the set_group_ban tool do? +

Mute group member. It is categorised as a Execute tool in the NapCat MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_group_ban? +

Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for set_group_ban: 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_ban? +

set_group_ban is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit set_group_ban? +

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

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

set_group_ban 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 → High-risk tools on this server →

Across the catalogue

set_breakpoint on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →