crow_store_memory

Store a new piece of information in persistent memory. Use this whenever you learn something important about the user, their projects, preferences, or any context that should persist across sessions.

SERVERCrow SOURCEkh0pper/crow
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-store-memory.md

What crow_store_memory does on Crow

AI agents use crow_store_memory to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.

Why crow_store_memory is rated Medium

This tool creates new data by writing information to persistent memory storage. It's a write operation (creation of stored data) that is reversible in principle (stored memories can typically be deleted). The blast radius is medium because an AI agent could store false or sensitive information that persists across sessions, potentially influencing future behavior, but it does not execute code or delete data.

From the tool's definition Store a new piece of information in persistent memory

Questions about crow_store_memory

What does the crow_store_memory tool do? +

Store a new piece of information in persistent memory. Use this whenever you learn something important about the user, their projects, preferences, or any context that should persist across sessions. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crow_store_memory? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_store_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.

What risk level is crow_store_memory? +

crow_store_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crow_store_memory? +

Yes. Add a rate_limit block to the crow_store_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.

How do I block crow_store_memory completely? +

Set action: deny in the PolicyLayer policy for crow_store_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.

What MCP server provides crow_store_memory? +

crow_store_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.

More on Crow, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.