hooks_intelligence_pattern-store

WHAT IT DOES

What hooks_intelligence_pattern-store does on Claude Flow

AI agents use hooks_intelligence_pattern-store 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.

WHY IT NEEDS A POLICY

Why hooks_intelligence_pattern-store needs a policy

The tool's primary action is storing (writing) a pattern into a persistent, indexed database (ReasoningBank with HNSW indexing). This is a reversible write operation — it creates new data but does not execute code, delete anything, or involve financial transactions. Misuse could pollute the reasoning/pattern store with malicious or misleading patterns, which could influence AI agent behavior, hence medium severity.

From the tool's definition 'Store pattern in ReasoningBank (HNSW-indexed)' — the tool writes/stores a new pattern entry into an indexed data store called ReasoningBank

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hooks_intelligence_pattern-store Rate-limited

hooks_intelligence_pattern-store stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_pattern-store": {
      "limits": [
        {
          "counter": "hooks_intelligence_pattern-store_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_pattern-store

What does the hooks_intelligence_pattern-store tool do? +

Store pattern in ReasoningBank (HNSW-indexed) 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.

How do I enforce a policy on hooks_intelligence_pattern-store? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_intelligence_pattern-store: 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_pattern-store? +

hooks_intelligence_pattern-store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hooks_intelligence_pattern-store? +

Yes. Add a rate_limit block to the hooks_intelligence_pattern-store 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_pattern-store completely? +

Set action: deny in the PolicyLayer policy for hooks_intelligence_pattern-store. 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_pattern-store? +

hooks_intelligence_pattern-store 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.