Send a message to a messenger channel
AI agents use dooray_send_channel_message to create or update resources in Dooray MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dooray MCP Server environment.
Sending a message is a write operation that creates new data in the Dooray system. While reversible (messages can be deleted via dooray_delete_comment or similar mechanisms), it modifies shared communication channels and could be misused to send spam, misinformation, or phishing content to other users.
From the tool's definition Tool description states 'Send a message to a messenger channel' - this creates new message data in a channel, a reversible write operation.
Attacks that exploit this kind of access
Send a message to a messenger channel. It is categorised as a Write tool in the Dooray MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for dooray_send_channel_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 Dooray MCP Server. Nothing to install.
dooray_send_channel_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 dooray_send_channel_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 dooray_send_channel_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.
dooray_send_channel_message is provided by the Dooray MCP Server MCP server (kwanok/dooray-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 →