This record as markdown: /tools/1021143806-napcat-mcp/set-group-whole-ban.md
What set_group_whole_ban does on NapCat MCP Server
AI agents invoke set_group_whole_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.
Why set_group_whole_ban is rated High
This tool executes a moderation action (whole-group mute) that affects all members of a group simultaneously. It is a reversible administrative action (mute can be lifted), so it falls under Execute rather than Destructive. However, the blast radius is high as it silences an entire group's membership instantly.
From the tool's definition 'Mute all members in group' — triggers a group-wide ban/mute operation affecting all members of a QQ group
Attacks that exploit this kind of access
The rule that runs set_group_whole_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_whole_ban, this is the rule to start with:
set_group_whole_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.
The button opens the PolicyLayer dashboard: create your workspace, connect NapCat MCP Server, apply this rule, and every set_group_whole_ban call is checked against it from then on.
Questions about set_group_whole_ban
Mute all members in group. 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.
Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for set_group_whole_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.
set_group_whole_ban is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_group_whole_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.
Set action: deny in the PolicyLayer policy for set_group_whole_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.
set_group_whole_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.
More on NapCat MCP Server, and thousands of servers like it.
Across the catalogue