AI agents use send_admin_message to create or update resources in Sendbird — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sendbird environment.
This tool creates new message data in a chat channel, which falls under the Write category (creates or modifies data reversibly). It is not Destructive because messages are not irreversibly deleted—they can be removed or edited.
From the tool's definition Tool 'send_admin_message' description states it can 'Inject an authoritative message into a chat channel from a specific user' and 'post system notices, automated responses, or moderation actions visible to all members.' This creates and modifies chat data…
Attacks that exploit this kind of access
Inject an authoritative message into a chat channel from a specific user. Used by AI agents to post system notices, automated responses, or moderation actions visible to all members. It is categorised as a Write tool in the Sendbird MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sendbird MCP server in PolicyLayer and add a rule for send_admin_message: 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.
send_admin_message 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 send_admin_message 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 send_admin_message. 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.
send_admin_message 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →