Create or update a memory file. The memory will be indexed for future recall.
AI agents use store_memory to create or update resources in Reporecall — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reporecall environment.
The tool creates or updates memory files, which modifies system state but is reversible (can be overwritten or cleared via other tools like clear_working_memory or compact_memories). This fits the Write category.
From the tool's definition Tool description states: "Create or update a memory file." These are reversible write operations that modify persistent data (memory storage).
Documented attack patterns abuse exactly the kind of access store_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for store_memory:
{
"version": "1",
"default": "deny",
"tools": {
"store_memory": {
"limits": [
{
"counter": "store_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}store_memory 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.
Create or update a memory file. The memory will be indexed for future recall. It is categorised as a Write tool in the Reporecall MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reporecall MCP server in PolicyLayer and add a rule for 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 Reporecall. Nothing to install.
store_memory 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 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.
Set action: deny in the PolicyLayer policy for 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.
store_memory is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.