hooks_intelligence_trajectory-end

WHAT IT DOES

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 IT NEEDS A POLICY

Why hooks_intelligence_trajectory-end needs a policy

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

Recommended rule Ready

Verdict

hooks_intelligence_trajectory-end Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_intelligence_trajectory-end": {
      "limits": [
        {
          "counter": "hooks_intelligence_trajectory-end_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about hooks_intelligence_trajectory-end

What does the hooks_intelligence_trajectory-end tool do? +

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.

How do I enforce a policy on hooks_intelligence_trajectory-end? +

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.

What risk level is hooks_intelligence_trajectory-end? +

hooks_intelligence_trajectory-end is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hooks_intelligence_trajectory-end? +

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.

How do I block hooks_intelligence_trajectory-end completely? +

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.

What MCP server provides hooks_intelligence_trajectory-end? +

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.