Restore an archived context or insight back to active.
AI agents use memcp_restore to create or update resources in Memcp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memcp environment.
This tool creates or modifies data reversibly—it reactivates archived memory, changing storage state without destructively deleting data. The operation is reversible (could be re-archived). While it affects persistent memory state, the impact is contained to the user's own memory store with no external side effects, justifying medium severity rather than high.
From the tool's definition Tool name 'memcp_restore' and description 'Restore an archived context or insight back to active' indicate the tool modifies state by moving data from archived to active status.
Documented attack patterns abuse exactly the kind of access memcp_restore gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memcp, and nothing reaches the server without passing your rules. This is the rule we recommend for memcp_restore:
{
"version": "1",
"default": "deny",
"tools": {
"memcp_restore": {
"limits": [
{
"counter": "memcp_restore_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memcp_restore 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.
Restore an archived context or insight back to active. It is categorised as a Write tool in the Memcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Me MCP server in PolicyLayer and add a rule for memcp_restore: 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 Memcp. Nothing to install.
memcp_restore 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 memcp_restore 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 memcp_restore. 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.
memcp_restore is provided by the Me MCP server (maydali28/memcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memcp, 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.
24 Memcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.