ban_disruptive_user · Sendbird MCP: Risk & Policy

WHAT IT DOES

What ban_disruptive_user does on Sendbird

AI agents invoke ban_disruptive_user to trigger actions in Sendbird. 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 IT NEEDS A POLICY

Why ban_disruptive_user needs a policy

Banning a user triggers an external moderation action that restricts a user's access to a channel. While it is time-limited (not permanent) and thus not fully irreversible, it has significant real-world impact on user access. It is not purely Write (not creating/modifying data records), but rather executing a moderation operation with external side effects.

From the tool's definition 'Ban a user from a specific channel for a set number of seconds' and 'enforce community guidelines'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ban_disruptive_user Rate-limited

ban_disruptive_user 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": {
    "ban_disruptive_user": {
      "limits": [
        {
          "counter": "ban_disruptive_user_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about ban_disruptive_user

What does the ban_disruptive_user tool do? +

Ban a user from a specific channel for a set number of seconds. Used by AI moderation agents to enforce community guidelines. Returns the ban end timestamp. It is categorised as a Execute tool in the Sendbird MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ban_disruptive_user? +

Register the Sendbird MCP server in PolicyLayer and add a rule for ban_disruptive_user: 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 Sendbird. Nothing to install.

What risk level is ban_disruptive_user? +

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

Can I rate-limit ban_disruptive_user? +

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

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

ban_disruptive_user is provided by the Sendbird MCP server (nobanks/sendbird-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.