memory_ingest · Exocortex MCP: Risk & Policy

WHAT IT DOES

What memory_ingest does on Exocortex

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

WHY IT NEEDS A POLICY

Why memory_ingest needs a policy

This tool writes/creates new memory entries into the system from various sources. It is a data ingestion operation that creates persistent records, which is reversible (memories can be deleted), placing it in the Write category. Misuse could pollute the memory system with malicious or misleading content, giving it medium severity.

From the tool's definition Ingest content into Exocortex from files, URLs, or session transcripts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

memory_ingest Rate-limited

memory_ingest 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_ingest": {
      "limits": [
        {
          "counter": "memory_ingest_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 Exocortex, so you can run agents against it safely.

FAQ

Questions about memory_ingest

What does the memory_ingest tool do? +

Ingest content into Exocortex from files, URLs, or session transcripts. It is categorised as a Write tool in the Exocortex 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_ingest? +

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

What risk level is memory_ingest? +

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

Can I rate-limit memory_ingest? +

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

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

memory_ingest is provided by the Exocortex MCP server (shawnhack/exocortex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.