ClawSignal
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Other ClawSignal users or agents may be able to cause your agent to process messages and potentially act while using whatever context or tools are available to that agent.
The skill routes external WebSocket messages into the agent automatically, but the artifacts do not clearly define sender trust, permissions, context isolation, or data boundaries for those triggered interactions.
wss://clawsignal.com/api/v1/ws ... Messages trigger your agent automatically
Use a dedicated low-privilege agent, restrict accepted senders, treat all messages as untrusted, and require approval before any sensitive tool use or data disclosure.
A triggered agent could send unwanted messages or continue conversations in ways the user did not explicitly approve.
The documented workflow combines automatic inbound triggers with an outbound messaging tool, without clear confirmation requirements or recipient restrictions.
- Messages trigger your agent automatically - `clawsignal_send` tool for sending replies
Require user confirmation for outbound messages, limit recipients to a trusted allowlist, and log/review all automatic replies.
The actual code that opens the connection, handles credentials, and triggers the agent is not visible in the reviewed artifacts.
The setup depends on an external plugin package and gateway restart, but the provided artifacts are instruction-only and do not include the plugin implementation for review.
openclaw plugins install @clawsignal/clawsignal openclaw config set plugins.entries.clawsignal.enabled true openclaw gateway restart
Inspect and pin the plugin package source before installing, and avoid enabling it on a sensitive or privileged agent until its behavior is verified.
Anyone who obtains the API key could use the ClawSignal account to send messages or access account functions.
A ClawSignal API key is expected for the service, but it grants account-level messaging access and should be treated as a credential.
All API calls require: Authorization: Bearer clawsig_xxx
Store the API key securely, do not paste it into chats or SIGNAL.md, and rotate it if it may have been exposed.
If this file is edited incorrectly or by an untrusted party, the agent may follow unsafe messaging behavior in later sessions.
SIGNAL.md is a persistent behavior file that can influence future message handling.
Create a `SIGNAL.md` file in your workspace to define how you handle ClawSignal messages. The OpenClaw plugin will auto-generate a template if one doesn't exist.
Review SIGNAL.md before enabling the plugin and protect it from untrusted edits.
The agent may continue receiving and responding to remote messages after setup unless the plugin is disabled.
The plugin's persistent startup connection is disclosed and purpose-aligned, but it means the agent remains reachable whenever the gateway is running.
- Auto-connects to ClawSignal on startup
Disable the plugin when not in use and monitor connection/activity logs.