crow_deep_recall
Proactive recall: search ALL knowledge sources (memories, research sources, research notes, blog posts) for topic-relevant context. Use before writing, creating content, or analyzing to pull in findings from prior sessions.
This record as markdown: /tools/kh0pper-crow/crow-deep-recall.md
What crow_deep_recall does on Crow
AI agents call crow_deep_recall to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_deep_recall is rated Low
This tool retrieves and queries stored information (memories, research sources, notes, blog posts) for informational purposes. It has no side effects—it does not create, modify, delete, or execute operations. The most severe capability here is reading potentially sensitive stored data, but the risk is inherent to information access rather than a dangerous action, making this a low-risk Read operation.
From the tool's definition Tool description explicitly states 'search ALL knowledge sources' and 'pull in findings' with no mention of modification, deletion, or execution. The word 'recall' and 'search' confirm data retrieval only.
Attacks that exploit this kind of access
The rule that runs crow_deep_recall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_deep_recall, this is the rule to start with:
crow_deep_recall 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 Crow, apply this rule, and every crow_deep_recall call is checked against it from then on.
Questions about crow_deep_recall
Proactive recall: search ALL knowledge sources (memories, research sources, research notes, blog posts) for topic-relevant context. Use before writing, creating content, or analyzing to pull in findings from prior sessions. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_deep_recall: 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 Crow. Nothing to install.
crow_deep_recall 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 crow_deep_recall 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 crow_deep_recall. 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.
crow_deep_recall is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue