set_group_whole_ban

Mute all members in group

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-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

Questions about set_group_whole_ban

What does the set_group_whole_ban tool do? +

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.

How do I enforce a policy on set_group_whole_ban? +

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.

What risk level is set_group_whole_ban? +

set_group_whole_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_whole_ban? +

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.

How do I block set_group_whole_ban completely? +

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.

What MCP server provides set_group_whole_ban? +

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.

// 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 NapCat 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.