set_group_admin
A write tool on the NapCat MCP server.
This record as markdown: /tools/1021143806-napcat-mcp/set-group-admin.md
What set_group_admin does on NapCat MCP Server
AI agents use set_group_admin to create or update resources in NapCat MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NapCat MCP Server environment.
Why set_group_admin is rated Medium
This tool creates or modifies group membership metadata (admin status) but does not irreversibly delete data or execute arbitrary code. It is reversible—admin status can be changed back. However, it carries high severity because granting admin privileges to unauthorized parties could enable malicious group control, message deletion, member removal, and other harmful actions through subsequent tool calls.
From the tool's definition Tool name 'set_group_admin' indicates modification of group administrative privileges. The server description notes 'group management' capabilities, and this tool directly modifies group member roles/permissions, which is a reversible structural change to…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs set_group_admin 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_admin, this is the rule to start with:
set_group_admin stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_admin call is checked against it from then on.
Questions about set_group_admin
set_group_admin is a write tool on the NapCat MCP Server MCP server. It is categorised as a Write tool in the NapCat MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for set_group_admin: 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_admin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_group_admin 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_admin. 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_admin 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.
This server
Across the catalogue