memory_link
A write tool on the Agent-Memory-OS MCP server.
This record as markdown: /tools/agent-memory-os/memory-link.md
What memory_link does on Agent-Memory-OS
AI agents use memory_link to create or update resources in Agent-Memory-OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent-Memory-OS environment.
Why memory_link is rated Medium
Without explicit documentation, we infer 'memory_link' likely creates or modifies relationships in the memory store (a Write operation). The blast radius is medium because unauthorized linking could corrupt memory associations used for agent decision-making, but effects are reversible via other memory management tools.
From the tool's definition Tool is named 'memory_link' with empty description, suggesting it creates associations or links in memory state. Sibling tools like 'memory_add' (Write), 'memory_consolidate' (Write), and 'memory_share' (Write) indicate this server modifies stored memory.
Attacks that exploit this kind of access
The rule that runs memory_link safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent-Memory-OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_link, this is the rule to start with:
memory_link 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 Agent-Memory-OS, apply this rule, and every memory_link call is checked against it from then on.
Questions about memory_link
memory_link is a write tool on the Agent-Memory-OS MCP server. It is categorised as a Write tool in the Agent-Memory-OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent-Memory-OS MCP server in PolicyLayer and add a rule for memory_link: 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 Agent-Memory-OS. Nothing to install.
memory_link 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 memory_link 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 memory_link. 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.
memory_link is provided by the Agent-Memory-OS MCP server (yamantaka520/Agent-Memory-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent-Memory-OS, and thousands of servers like it.
This server
Across the catalogue