memory_import_codex
AI agents use memory_import_codex to create or update resources in Locus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Locus environment.
The tool appears to import external data (likely code context or knowledge) into Locus's local persistent memory store, which constitutes creation or modification of stored data. This is reversible (unlike purge/forget) and does not execute external code or move money. However, confidence is moderate because the description is empty, requiring inference from the name and sibling tools.
From the tool's definition Tool name 'memory_import_codex' suggests importing/loading data into the persistent memory system. The 'import' prefix indicates data ingestion and modification of stored state.
Documented attack patterns abuse exactly the kind of access memory_import_codex gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Locus, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_import_codex:
{
"version": "1",
"default": "deny",
"tools": {
"memory_import_codex": {
"limits": [
{
"counter": "memory_import_codex_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memory_import_codex 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.
memory_import_codex. It is categorised as a Write tool in the Locus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Locus MCP server in PolicyLayer and add a rule for memory_import_codex: 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 Locus. Nothing to install.
memory_import_codex 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_import_codex 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_import_codex. 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_import_codex is provided by the Locus MCP server (magnifico4625/locus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Locus, 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.
17 Locus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.