set_group_leave · NapCat MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_group_leave does on NapCat MCP Server

AI agents use set_group_leave 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 IT NEEDS A POLICY

Why set_group_leave needs a policy

An AI agent can call set_group_leave faster than any human can review — one bad instruction and it creates or modifies resources in NapCat MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_group_leave Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_group_leave": {
      "limits": [
        {
          "counter": "set_group_leave_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches NapCat MCP Server, so you can run agents against it safely.

FAQ

Questions about set_group_leave

What does the set_group_leave tool do? +

Leave or dismiss group. 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.

How do I enforce a policy on set_group_leave? +

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

set_group_leave is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_group_leave? +

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

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

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

// THE FULL RECORD

set_group_leave is one line of NapCat MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →