remember
AI agents use remember to create or update resources in Astria-Index — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Astria-Index environment.
The tool stores or creates data (memories/notes) in a persistent system without deleting or executing external operations. This is a Write operation (reversible data creation). Medium severity because misuse could pollute an AI's memory with false information, affecting subsequent decisions, but effects are limited to the user's own memory system and are reversible via the 'forget' tool.
From the tool's definition Tool name 'remember' combined with server context describing 'persistent recall' and 'memory' functionality indicates data storage/creation.
Attacks that exploit this kind of access
remember. It is categorised as a Write tool in the Astria-Index MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Astria-Index 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 Astria-Index. 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 Astria-Index MCP server (pl-odin/astria-plugin). 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 →