memory.inbox_reject · Lore Context MCP: Risk & Policy

WHAT IT DOES

What memory.inbox_reject does on Lore Context

AI agents use memory.inbox_reject 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.inbox_reject needs a policy

This tool creates or modifies data reversibly by changing the status of a memory candidate from pending review to rejected. It is not a Read operation (it has side effects beyond querying), not Execute (does not run arbitrary code or trigger external operations), not Destructive (rejection can presumably be undone or appealed in a governance system), and not Financial.

From the tool's definition Tool name 'memory.inbox_reject' and description 'Reject a memory candidate from the governance review queue. Requires a reason.' indicate the tool modifies the state of a memory governance system by removing/rejecting items from a queue.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory.inbox_reject Rate-limited

memory.inbox_reject 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.inbox_reject": {
      "limits": [
        {
          "counter": "memory.inbox_reject_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.inbox_reject

What does the memory.inbox_reject tool do? +

Reject a memory candidate from the governance review queue. Requires a reason. 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.inbox_reject? +

Register the Lore Context MCP server in PolicyLayer and add a rule for memory.inbox_reject: 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.inbox_reject? +

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

Can I rate-limit memory.inbox_reject? +

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

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

memory.inbox_reject 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.