Store a memory for later recall. Agents remember across sessions. Include project and branch for scoped recall.
AI agents use corn_memory_store to create or update resources in CornMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CornMCP environment.
This tool writes data (memories) to persistent storage for later retrieval. It creates/modifies stored state but is reversible in principle. The cross-session persistence increases severity slightly as misuse could pollute an agent's long-term memory context, but it does not execute code or destroy data irreversibly.
From the tool's definition 'Store a memory for later recall. Agents remember across sessions.'
Documented attack patterns abuse exactly the kind of access corn_memory_store gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CornMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for corn_memory_store:
{
"version": "1",
"default": "deny",
"tools": {
"corn_memory_store": {
"limits": [
{
"counter": "corn_memory_store_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}corn_memory_store stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Store a memory for later recall. Agents remember across sessions. Include project and branch for scoped recall. It is categorised as a Write tool in the CornMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Corn MCP server in PolicyLayer and add a rule for corn_memory_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 CornMCP. Nothing to install.
corn_memory_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 corn_memory_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 corn_memory_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.
corn_memory_store is provided by the Corn MCP server (yuki-20/cornmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 CornMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 CornMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.