Save a memory, insight, decision, or context fragment to the unified OmegaBrain vault.
AI agents use omega_remember to create or update resources in Mcp-Omega-Brain — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp-Omega-Brain environment.
An AI agent can call omega_remember faster than any human can review — one bad instruction and it creates or modifies resources in Mcp-Omega-Brain by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Save a memory, insight, decision, or context fragment to the unified OmegaBrain vault. It is categorised as a Write tool in the Mcp-Omega-Brain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp-Omega-Brain MCP server in PolicyLayer and add a rule for omega_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 Mcp-Omega-Brain. Nothing to install.
omega_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 omega_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 omega_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.
omega_remember is provided by the Mcp-Omega-Brain MCP server (vrtxomega/omega-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.