hooks_intelligence_pattern-store
Store pattern in ReasoningBank (HNSW-indexed) Use when native Bash hooks (via Claude Code\
This record as markdown: /tools/io-github-ruvnet-claude-flow/hooks-intelligence-pattern-store.md
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 hooks_intelligence_pattern-store is rated Medium
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
The rule that runs hooks_intelligence_pattern-store 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_pattern-store, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every hooks_intelligence_pattern-store call is checked against it from then on.
Questions about hooks_intelligence_pattern-store
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.
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.
hooks_intelligence_pattern-store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue