시맨틱 메모리에 project_id·session_id 스코프로 저장합니다. 동일 key는 upsert됩니다.
AI agents use save_memory to create or update resources in Infinite Context Keeper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infinite Context Keeper environment.
An AI agent can call save_memory faster than any human can review — one bad instruction and it creates or modifies resources in Infinite Context Keeper by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
시맨틱 메모리에 project_id·session_id 스코프로 저장합니다. 동일 key는 upsert됩니다. It is categorised as a Write tool in the Infinite Context Keeper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Infinite Context Keeper MCP server in PolicyLayer and add a rule for save_memory: 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 Infinite Context Keeper. Nothing to install.
save_memory 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 save_memory 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 save_memory. 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.
save_memory is provided by the Infinite Context Keeper MCP server (sujkh85/infinite-context-keeper-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.