Write a memory file at /memories/<path> with the supplied file_text. Overwrites if the file exists. Persists to sled, content-addresses the bytes (file_cid), and signs the write so the operation carries a verifiable receipt. Mirrors the create verb in Anthropic's context-management-2025-06-27 mem...
Risk signalsAccepts file system path (path)
Part of the emem — Earth memory protocol server.
Free to start. No card required.
AI agents use memory_create to create or modify resources in emem — Earth memory protocol. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call memory_create repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach emem — Earth memory protocol.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"memory_create": {
"limits": [
{
"counter": "memory_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full emem — Earth memory protocol policy for all 81 tools.
These attack patterns abuse exactly the kind of access memory_create gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Write a memory file at /memories/<path> with the supplied file_text. Overwrites if the file exists. Persists to sled, content-addresses the bytes (file_cid), and signs the write so the operation carries a verifiable receipt. Mirrors the create verb in Anthropic's context-management-2025-06-27 memory tool spec. When to use: Call when the LLM issues a create against its memory directory (initial scratchpad write, refresh of a notes file, etc.). The response carries the new file_cid and a signed receipt the agent can quote in audits.. It is categorised as a Write tool in the emem — Earth memory protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the emem — Earth memory protocol MCP server in PolicyLayer and add a rule for memory_create: 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 emem — Earth memory protocol. Nothing to install.
memory_create 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 memory_create 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 memory_create. 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.
memory_create is provided by the emem — Earth memory protocol MCP server (oci:ghcr.io/vortx-ai/emem:latest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 81 emem — Earth memory protocol tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.