CALL IMMEDIATELY when user explicitly asks to remember/record something.\n\n
AI agents use remember to create or update resources in Codebase Context — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codebase Context environment.
This tool records or stores information (memories/notes) when instructed by the user. It creates or modifies persistent data, which is a Write operation. The description is sparse, but 'remember/record' clearly implies writing to some storage. It is reversible in principle (stored data can typically be deleted), so it does not qualify as Destructive.
From the tool's definition Tool name 'remember' and description 'CALL IMMEDIATELY when user explicitly asks to remember/record something' indicate writing/storing data persistently.
Documented attack patterns abuse exactly the kind of access remember gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codebase Context, and nothing reaches the server without passing your rules. This is the rule we recommend for remember:
{
"version": "1",
"default": "deny",
"tools": {
"remember": {
"limits": [
{
"counter": "remember_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}remember 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.
CALL IMMEDIATELY when user explicitly asks to remember/record something.\n\n. It is categorised as a Write tool in the Codebase Context MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codebase Context MCP server in PolicyLayer and add a rule for remember: 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 Codebase Context. Nothing to install.
remember 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 remember 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 remember. 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.
remember is provided by the Codebase Context MCP server (patricksys/codebase-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Codebase Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Codebase Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.