Validate whether a memory was helpful. Helpful increases confidence by +0.1, unhelpful decreases by -0.05.
AI agents use memory_validate to create or update resources in Claude Persistent Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Persistent Memory environment.
The tool updates a numeric confidence attribute on a stored memory entry based on a helpfulness signal. This is a reversible modification of existing data (a score adjustment), placing it in the Write category. The blast radius is low since it only adjusts a floating-point weight on a memory record and does not delete or expose sensitive data.
From the tool's definition 'Helpful increases confidence by +0.1, unhelpful decreases by -0.05' — modifies the confidence score of an existing memory record
Documented attack patterns abuse exactly the kind of access memory_validate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Persistent Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_validate:
{
"version": "1",
"default": "deny",
"tools": {
"memory_validate": {
"limits": [
{
"counter": "memory_validate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memory_validate 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.
Validate whether a memory was helpful. Helpful increases confidence by +0.1, unhelpful decreases by -0.05. It is categorised as a Write tool in the Claude Persistent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Persistent Memory MCP server in PolicyLayer and add a rule for memory_validate: 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 Claude Persistent Memory. Nothing to install.
memory_validate 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_validate 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_validate. 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_validate is provided by the Claude Persistent Memory MCP server (mimi180306/claude-persistent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Persistent Memory, 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.
4 Claude Persistent Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.