other
- Location
SKILL.md:11- Finding
Broad Retrieval of Persistent User Conversation History
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:11-66
Vulnerability Type: Sensitive conversation history access
Risk Level: MediumVulnerable Instruction Snippets
markdown - **Automatic recall (hook):** At the start of each turn, the system runs a memory search using the user's current message and injects relevant past memories into your context. You do not need to call any tool for that. - **When that is not enough:** If the user's message is very long, vague, or the automatic search returns **no memories**, you should **generate your own short, focused query** and call `memory_search` yourself.markdown ### task_summary - **What it does:** Returns the full task summary for a given `task_id`: title, status, and the complete narrative summary of that conversation task (steps, decisions, URLs, commands, etc.). - **When to call:** A `memory_search` hit included a `task_id` and you need the full story of that task (e.g. what was done, what the user decided, what failed or succeeded).markdown ### memory_timeline - **What it does:** Expands context around a single memory chunk: returns the surrounding conversation messages (±N turns) so you see what was said before and after that excerpt. - **When to call:** A `memory_search` hit is relevant but you need the surrounding dialogue (e.g. who said what next, or the exact follow-up question). - **Parameters:** `chunkId` (from a search hit), optional `window` (default 2). - **Effect:** You get a short, linear slice of the conversation around that chunk.Technical Analysis
The skill instructs the agent to consume automatically recalled long-term conversation data on every turn and to perform additional self-generated searches when no memory is initially returned. Search results can then be expanded through
task_summaryandmemory_timeline, exposing complete task narratives and surrounding messages rather than only the minimu ...[truncated 2066 chars]- Remediation
View remediation
Remediation Suggestions
- Require explicit user consent before searching or expanding persistent conversation history.
- Disable automatic recall by default, or limit it to clearly defined use cases where historical context is necessary.
- Restrict every memory query to the current task and retrieve only the minimum relevant fields.
- Do not automatically issue a new search merely because no memory block is present; first determine whether historical information is required.
- Require separate confirmation before invoking
task_summaryormemory_timeline, because these operations expand the amount of exposed data. - Apply authorization checks so the active user and agent can access only memory records belonging to the correct account and permitted scope.
- Redact credentials, authentication tokens, sensitive URLs, personal data, and confidential command output before memory content is returned.
- Add limits for result count, timeline window, task-summary size, and retention period.
- Record memory searches and expansion operations in an audit log visible to the user.
- Treat recalled content as untrusted data rather than instructions, preventing historical prompt content from changing system policies or tool authorization.
