memento_record_memory_hit · Memento MCP: Risk & Policy

WHAT IT DOES

What memento_record_memory_hit does on Memento

AI agents use memento_record_memory_hit to create or update resources in Memento — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memento environment.

WHY IT NEEDS A POLICY

Why memento_record_memory_hit needs a policy

This tool writes metadata to the memory system by recording access events and adjusting relevance scores. It modifies existing data (relevance/ranking) but does so reversibly and non-destructively. No code execution, deletion, or financial action is involved. Severity is low since it only affects internal memory relevance scores.

From the tool's definition Manually record that specific memories were accessed/used. Boosts their relevance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memento_record_memory_hit Rate-limited

memento_record_memory_hit 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memento_record_memory_hit": {
      "limits": [
        {
          "counter": "memento_record_memory_hit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Memento, so you can run agents against it safely.

FAQ

Questions about memento_record_memory_hit

What does the memento_record_memory_hit tool do? +

[DEPRECATED] Manually record that specific memories were accessed/used. Boosts their relevance. It is categorised as a Write tool in the Memento MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memento_record_memory_hit? +

Register the Memento MCP server in PolicyLayer and add a rule for memento_record_memory_hit: 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 Memento. Nothing to install.

What risk level is memento_record_memory_hit? +

memento_record_memory_hit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memento_record_memory_hit? +

Yes. Add a rate_limit block to the memento_record_memory_hit 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.

How do I block memento_record_memory_hit completely? +

Set action: deny in the PolicyLayer policy for memento_record_memory_hit. 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.

What MCP server provides memento_record_memory_hit? +

memento_record_memory_hit is provided by the Memento MCP server (joyciakira/memento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.