Send cross-agent notification Use when native Bash hooks (via Claude Code\
AI agents use hooks_notify to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
The tool sends notifications to other agents, which is a write/trigger action with side effects on other running agents. It does not appear to execute arbitrary code or delete data, but cross-agent messaging in a hive-mind orchestration system could have meaningful blast radius if misused (e.g., flooding agents or sending malicious signals). Truncated description reduces confidence.
From the tool's definition 'Send cross-agent notification' — triggers a notification event across agents; description is truncated ('via Claude Code\') limiting full assessment
Attacks that exploit this kind of access
Send cross-agent notification Use when native Bash hooks (via Claude Code\. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_notify: 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 Claude Flow. Nothing to install.
hooks_notify 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 hooks_notify 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 hooks_notify. 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.
hooks_notify is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.