agentdb_pattern-search
Search patterns via ReasoningBank controller with BM25+semantic hybrid Use when generic memory_* tools are wrong because you need AgentDB-specific controllers (HNSW vector search, hierarchical tiers, causal-graph links, pattern store/recall, RaBitQ quantization). For simple key-value persistence,...
This record as markdown: /tools/ruflo/agentdb-pattern-search.md
What agentdb_pattern-search does on Ruflo
AI agents call agentdb_pattern-search to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why agentdb_pattern-search is rated Low
This is a read-only search and retrieval tool. It queries existing pattern data using hybrid search methods (BM25 and semantic search) but does not modify, execute, delete, or commit financial actions. The tool is explicitly positioned as an alternative to generic memory tools for specialized search scenarios, confirming its read-only nature.
From the tool's definition Tool performs 'Search patterns via ReasoningBank controller with BM25+semantic hybrid', explicitly described as a search operation.
Attacks that exploit this kind of access
The rule that runs agentdb_pattern-search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agentdb_pattern-search, this is the rule to start with:
agentdb_pattern-search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every agentdb_pattern-search call is checked against it from then on.
Questions about agentdb_pattern-search
Search patterns via ReasoningBank controller with BM25+semantic hybrid Use when generic memory_* tools are wrong because you need AgentDB-specific controllers (HNSW vector search, hierarchical tiers, causal-graph links, pattern store/recall, RaBitQ quantization). For simple key-value persistence, memory_store/memory_retrieve are simpler. For unrelated file work, native Read/Write are fine. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for agentdb_pattern-search: 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.
agentdb_pattern-search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agentdb_pattern-search 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 agentdb_pattern-search. 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.
agentdb_pattern-search 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.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue