Link skill to memory (establishes reference relationship). WHAT: Creates a bidirectional association between a skill and a memory via the memory_skill_association table. WHEN: When a memory mentions or relates to a skill, or when procedural knowledge (skill) should be discoverable from declarativ...
AI agents use link_skill_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 and modifies data relationships (associations) in a reversible manner. It does not read-only, does not execute external code, and does not irreversibly delete data. The tool is idempotent and safe to call multiple times, which is consistent with a Write operation.
From the tool's definition Creates a bidirectional association between a skill and a memory via the memory_skill_association table. The tool establishes reference relationships that link data together.
Documented attack patterns abuse exactly the kind of access link_skill_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_skill_to_memory:
{
"version": "1",
"default": "deny",
"tools": {
"link_skill_to_memory": {
"limits": [
{
"counter": "link_skill_to_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link_skill_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 skill to memory (establishes reference relationship). WHAT: Creates a bidirectional association between a skill and a memory via the memory_skill_association table. WHEN: When a memory mentions or relates to a skill, or when procedural knowledge (skill) should be discoverable from declarative knowledge (memory) and vice versa. BEHAVIOR: Creates association between skill and memory. Idempotent - safe to call multiple times (won't create duplicates). Both skill and memory must exist and be owned by the user. Examples: # After creating a skill about deployment: link_skill_to_memory(skill_id=5, memory_id=123) # Connect a testing skill to a testing decision memory: link_skill_to_memory(skill_id=8, memory_id=456) Args: skill_id: Skill ID to link memory_id: Memory ID to link ctx: Context (automatically injected) Returns: Confirmation dict with success status Raises: ToolError: If skill 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_skill_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_skill_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_skill_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_skill_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_skill_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.