memory.add_candidate · Lore Context MCP: Risk & Policy

WHAT IT DOES

What memory.add_candidate does on Lore Context

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

WHY IT NEEDS A POLICY

Why memory.add_candidate needs a policy

This tool writes new memory candidates to a governed memory system. While reversible (candidates can be removed or replaced), it modifies persistent state that influences the AI agent's context and reasoning. The 'governed' qualifier and 'beta' designation suggest controls are in place, preventing this from being destructive.

From the tool's definition 'Add a beta memory candidate through governed memory writeback' — the verb 'Add' and 'writeback' indicate the tool creates or modifies data in a memory system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory.add_candidate Rate-limited

memory.add_candidate 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": {
    "memory.add_candidate": {
      "limits": [
        {
          "counter": "memory.add_candidate_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 Lore Context, so you can run agents against it safely.

FAQ

Questions about memory.add_candidate

What does the memory.add_candidate tool do? +

Add a beta memory candidate through governed memory writeback. It is categorised as a Write tool in the Lore Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory.add_candidate? +

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

What risk level is memory.add_candidate? +

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

Can I rate-limit memory.add_candidate? +

Yes. Add a rate_limit block to the memory.add_candidate 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 memory.add_candidate completely? +

Set action: deny in the PolicyLayer policy for memory.add_candidate. 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 memory.add_candidate? +

memory.add_candidate is provided by the Lore Context MCP server (Lore-Context/lore-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.