hooks_intelligence_trajectory-end
End trajectory and trigger SONA learning with EWC++ Use when native Bash hooks (via Claude Code\
This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-intelligence-trajectory-end.md
What hooks_intelligence_trajectory-end does on Claude Flow
AI agents invoke hooks_intelligence_trajectory-end to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why hooks_intelligence_trajectory-end is rated High
This tool executes machine learning operations (SONA learning with EWC++) and invokes Bash hooks, making it Execute rather than Read or Write. While it modifies agent learning state, the critical mechanism is the execution of trajectory termination and learning triggers. In a swarm/orchestration context, this could affect multiple agents' behavior.
From the tool's definition Tool name indicates 'trajectory-end' which triggers 'SONA learning with EWC++' — a machine learning operation. Description mentions 'native Bash hooks' suggesting command execution.
Attacks that exploit this kind of access
The rule that runs hooks_intelligence_trajectory-end safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_intelligence_trajectory-end, this is the rule to start with:
hooks_intelligence_trajectory-end stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hooks_intelligence_trajectory-end call is checked against it from then on.
Questions about hooks_intelligence_trajectory-end
End trajectory and trigger SONA learning with EWC++ Use when native Bash hooks (via Claude Code\. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_intelligence_trajectory-end: 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_intelligence_trajectory-end is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hooks_intelligence_trajectory-end 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_intelligence_trajectory-end. 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_intelligence_trajectory-end 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.
More on Claude Flow, and thousands of servers like it.
Across the catalogue