hooks_session-start

What hooks_session-start does on Claude Flow

AI agents invoke hooks_session-start 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_session-start is rated High

This tool triggers initialization and daemon startup—external operations whose effects depend on configuration and runtime state. While not destructive per se, it executes background processes which can alter system state, consume resources, or enable further actions. Classified as Execute rather than Write because it runs code/processes rather than just creating reversible data artifacts.

From the tool's definition Tool name 'hooks_session-start' with description 'Initialize a new session and auto-start daemon' indicates launching background processes or daemon initialization. The mention of 'native Bash hooks' and 'Claude Code' confirms command execution capabilities.

The rule that runs hooks_session-start 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_session-start, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hooks_session-start": {
      "limits": [
        {
          "counter": "hooks_session-start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about hooks_session-start