AI agents invoke hooks_intelligence_trajectory-end to trigger actions in Ruflo. 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.
The tool ends a trajectory and triggers SONA learning via Bash hooks, which constitutes execution of potentially complex operations in an autonomous agent swarm system. The blast radius is high because trajectory termination and EWC++ learning triggers could affect swarm behavior, memory states, and agent coordination.
From the tool's definition Tool name references 'trajectory-end' and description states 'trigger SONA learning with EWC++' and 'native Bash hooks'. The mention of triggering learning systems and Bash hook execution indicates this initiates code execution workflows.
Attacks that exploit this kind of access
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 Ruflo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ruflo 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
hooks_intelligence_trajectory-end is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →