Link entity to memory (establishes reference relationship). WHEN: When a memory mentions or relates to an entity. Creates bidirectional link so the entity can be discovered from the memory and vice versa. BEHAVIOR: Creates association between entity and memory. Idempotent - safe to call multiple ...
AI agents use link_entity_to_memory to create or update resources in Forgetful — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgetful environment.
This tool creates new data (associations/links) in the persistent storage system, making it a Write operation. It is reversible (links can presumably be removed), so it does not qualify as Destructive.
From the tool's definition The tool description states it "Creates association between entity and memory" and "establishes reference relationship." This is a data modification operation that creates a new bidirectional link structure in the knowledge base.
Documented attack patterns abuse exactly the kind of access link_entity_to_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for link_entity_to_memory:
{
"version": "1",
"default": "deny",
"tools": {
"link_entity_to_memory": {
"limits": [
{
"counter": "link_entity_to_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link_entity_to_memory 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.
Free to start. No card required.
Link entity to memory (establishes reference relationship). WHEN: When a memory mentions or relates to an entity. Creates bidirectional link so the entity can be discovered from the memory and vice versa. BEHAVIOR: Creates association between entity and memory. Idempotent - safe to call multiple times (won't create duplicates). Both entity and memory must exist and be owned by the user. Examples: # After creating memory about a technical decision: link_entity_to_memory(entity_id=5, memory_id=123) # Link to decision maker # After creating memory about a system issue: link_entity_to_memory(entity_id=12, memory_id=456) # Link to affected server Args: entity_id: Entity ID to link memory_id: Memory ID to link ctx: Context (automatically injected) Returns: True if linked successfully (or already linked) Raises: ToolError: If entity or memory not found or not owned by user. It is categorised as a Write tool in the Forgetful MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgetful MCP server in PolicyLayer and add a rule for link_entity_to_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 Forgetful. Nothing to install.
link_entity_to_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 link_entity_to_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 link_entity_to_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.
link_entity_to_memory is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.