10 tools from the Memolink MCP Server, categorised by risk level.
View the Memolink policy →get_daily_summary Retrieves the user's journal entries from a specific day to provide context about their current state or activities. get_goals Fetches current, active, completed, or archived goals the user is working towards in their life or projects. get_user_tags Fetches all existing tags used by the user. Run this to know what categories already exist before saving new memos or goals. list_memos List memos and research notes with pagination. Call this when the user wants to browse their library of notes, or when searching isn't yielding the... read_memo Retrieve a specific memo or journal entry by its explicit ID to get its full context and details. search_memos Searches past memos and journal entries to retrieve context about the user. Very useful for fetching previous reflections, facts, or projects. create_goal Creates a new goal for the user to track in Memolink. 2/5 create_memo Creates a new personalized journal entry or memo in Memolink. Always use this to save facts, reflections, or context about the user's life. 2/5 update_memo Update an existing memo. Use this to append or correct facts about the user for a memory you already know the ID of. 2/5 The Memolink MCP server exposes 10 tools across 3 categories: Read, Write, Destructive.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Memolink server.
Memolink tools are categorised as Read (6), Write (3), Destructive (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept