Fetch a single memory by ID. Returns a compact JSON blob with id, content, category, importance, tags, and timestamps. Used by the dashboard
AI agents call crow_get_memory to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored memory data by ID and returns structured metadata. It performs a query operation with no capability to modify, delete, or execute actions. The read-only nature and return of a JSON blob confirm classification as a Read operation with low severity—an AI agent misusing it would only access existing memory content, posing minimal risk unless the memory contains highly sensitive data, but…
From the tool's definition Tool name 'crow_get_memory' and description 'Fetch a single memory by ID. Returns a compact JSON blob...' indicate pure retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access crow_get_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_get_memory:
{
"version": "1",
"default": "deny",
"tools": {
"crow_get_memory": {}
}
}crow_get_memory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a single memory by ID. Returns a compact JSON blob with id, content, category, importance, tags, and timestamps. Used by the dashboard. 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_get_memory: 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_get_memory 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_get_memory 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_get_memory. 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_get_memory 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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.