Save a fact under key. Overwrites existing entry. Optional ISO-8601 expires.
AI agents use remember to create or update resources in Nexus Core — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nexus Core environment.
This is a straightforward data-write operation. It stores or updates a key-value pair in what is likely a personal knowledge base or fact store. The 'Overwrites existing entry' language indicates modification of existing records, which is classic Write behavior. The optional expiration parameter adds time-bound metadata but does not change the core category.
From the tool's definition 'Save a fact under `key`. Overwrites existing entry.' — the tool creates and modifies data (writes facts to storage), with reversible semantics (overwrite, not deletion). No permanent destruction, no external execution, no financial impact.
Attacks that exploit this kind of access
Save a fact under key. Overwrites existing entry. Optional ISO-8601 expires. It is categorised as a Write tool in the Nexus Core MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nexus Core 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 Nexus Core. 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 Nexus Core MCP server (noumenon-ai/nexus-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →