Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [Slack] openclaw message send bypasses dmPolicy allowlist for outbound DMs [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77812•Fetched 2026-05-06 06:20:59
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
dab02dab02
Participants
clawsweeper[bot]clawsweeper[bot]dab02dab02
Timeline (top)
commented ×1labeled ×1

The openclaw message send CLI command can send DMs to any user in the Slack workspace, even when channels.slack.dmPolicy: "allowlist" is configured with a restricted allowFrom list.

Config

"channels": {
  "slack": {
    "dmPolicy": "allowlist",
    "allowFrom": ["U13SPRCE7"]
  }
}

Root Cause

unning openclaw message send --channel slack --target "U015WTU317C" should be blocked because U015WTU317C is not in allowFrom.

Code Example

"channels": {
  "slack": {
    "dmPolicy": "allowlist",
    "allowFrom": ["U13SPRCE7"]
  }
}

### Steps to reproduce

1. Run: openclaw message send --channel slack --target "U_OTHER_USER" --message "test"
2. Message is delivered successfully despite user not being in allowlist

### Expected behavior

unning openclaw message send --channel slack --target "U015WTU317C" should be blocked because U015WTU317C is not in allowFrom.

### Actual behavior

Message is sent successfully, bypassing the allowlist restriction.


### OpenClaw version

2026.5.2

### Operating system

Ubuntu 24.04

### Install method

_No response_

### Model

opus 4.1

### Provider / routing chain

openclaw - opus 4.1.

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The openclaw message send CLI command can send DMs to any user in the Slack workspace, even when channels.slack.dmPolicy: "allowlist" is configured with a restricted allowFrom list.

Config

"channels": {
  "slack": {
    "dmPolicy": "allowlist",
    "allowFrom": ["U13SPRCE7"]
  }
}

### Steps to reproduce

1. Run: openclaw message send --channel slack --target "U_OTHER_USER" --message "test"
2. Message is delivered successfully despite user not being in allowlist

### Expected behavior

unning openclaw message send --channel slack --target "U015WTU317C" should be blocked because U015WTU317C is not in allowFrom.

### Actual behavior

Message is sent successfully, bypassing the allowlist restriction.


### OpenClaw version

2026.5.2

### Operating system

Ubuntu 24.04

### Install method

_No response_

### Model

opus 4.1

### Provider / routing chain

openclaw - opus 4.1.

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

Security — agents can bypass their own DM restrictions via CLI tool, enabling unintended outbound messages to workspace members.

Additional information

Suggested fix: openclaw message send should validate target against dmPolicy + allowFrom before sending, or add separate outboundPolicy / outboundAllowTo config.

extent analysis

TL;DR

The openclaw message send CLI command should be updated to validate the target user against the dmPolicy and allowFrom configuration before sending direct messages.

Guidance

  • Review the openclaw message send command's implementation to ensure it checks the dmPolicy and allowFrom configuration before sending a message.
  • Consider adding a separate outboundPolicy or outboundAllowTo configuration to provide more fine-grained control over direct message sending.
  • Verify that the allowFrom list is correctly populated and that the target user is not in the list before sending a message.
  • Test the openclaw message send command with different configurations and target users to ensure the fix works as expected.

Example

No code snippet is provided as the issue does not contain sufficient implementation details.

Notes

The suggested fix implies that the current implementation of the openclaw message send command does not properly enforce the dmPolicy and allowFrom configuration, allowing agents to bypass their own DM restrictions.

Recommendation

Apply a workaround by modifying the openclaw message send command to validate the target user against the dmPolicy and allowFrom configuration before sending a message, as this will address the security vulnerability and prevent unintended outbound messages.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

unning openclaw message send --channel slack --target "U015WTU317C" should be blocked because U015WTU317C is not in allowFrom.

#device allocation#model download#tokenizer error#prompt formatting#chain error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: [Slack] openclaw message send bypasses dmPolicy allowlist for outbound DMs [1 comments, 2 participants]