roam_remember
Add a memory or piece of information to remember, stored on the daily page with ROAM_MEMORIES_TAG tag and optional categories (unless include_memories_tag is false). \nNOTE on Roam-flavored markdown: For direct linking: use [[link]] syntax. For aliased linking, use [alias]([[link]]) syntax. Do no...
This record as markdown: /tools/2b3pro-roam-research-mcp/roam-remember.md
What roam_remember does on Roam Research
AI agents use roam_remember to create or update resources in Roam Research, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Roam Research environment.
Why roam_remember is rated Medium
The tool creates and stores new data (memories) in the Roam Research graph, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move financial resources. While it modifies the user's personal knowledge base, the scope is limited to adding information to a designated memory store.
From the tool's definition Tool description states 'Add a memory or piece of information to remember, stored on the daily page' - the verb 'Add' indicates creation/modification of data. This creates new entries in the user's knowledge graph.
Attacks that exploit this kind of access
The rule that runs roam_remember safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Roam Research, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For roam_remember, this is the rule to start with:
roam_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Roam Research, apply this rule, and every roam_remember call is checked against it from then on.
Questions about roam_remember
Add a memory or piece of information to remember, stored on the daily page with ROAM_MEMORIES_TAG tag and optional categories (unless include_memories_tag is false). \nNOTE on Roam-flavored markdown: For direct linking: use [[link]] syntax. For aliased linking, use [alias]([[link]]) syntax. Do not concatenate words in links/hashtags - correct: #[[multiple words]] #self-esteem (for typically hyphenated words).\nIMPORTANT: Before using this tool, ensure that you have loaded into context the \. It is categorised as a Write tool in the Roam Research MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Roam Research MCP server in PolicyLayer and add a rule for roam_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 Roam Research. Nothing to install.
roam_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 roam_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 roam_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.
roam_remember is provided by the Roam Research MCP server (2b3pro/roam-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Roam Research, and thousands of servers like it.
This server
Across the catalogue