AI agents use hooks_intelligence_pattern-store to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
The tool stores patterns into a vector database (ReasoningBank with HNSW indexing). This is a Write operation as it creates/modifies persisted data in the index. It is reversible in principle (patterns can be deleted), so it does not rise to Destructive.
From the tool's definition 'Store pattern in ReasoningBank (HNSW-indexed)' — explicitly writes/persists data to an indexed store
Attacks that exploit this kind of access
Store pattern in ReasoningBank (HNSW-indexed) Use when native Bash hooks (via Claude Code\. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo 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 Ruflo. 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 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_pattern-store 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 →