Mb Db Workflow

• Outcome: Review
• Latest audit: Jul 23, 2026 · 6:20 PM UTC
• Version: 1.0.0

Overview

This is a local Memory Bank helper, but it needs review because its broad triggers and inconsistent approval rules could lead to persistent project-state updates the user did not clearly ask for.

Install only for repositories that intentionally use mb-cli with memory-bank/database. Before relying on it, narrow the activation language and require explicit user approval before any mb command that creates, updates, deletes, syncs, or regenerates files.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (4)

Intent-Code Divergence

Medium

• Confidence: 96% confidence
• Finding: The session-management workflow tells the agent to create a missing session file automatically, which conflicts with the earlier rule requiring explicit user approval before any file modification or creation. In a skill that records project state via mb-cli, this can cause unauthorized writes and normalizes bypassing user consent controls.

Intent-Code Divergence

Medium

• Confidence: 98% confidence
• Finding: The memory-bank update workflow directs the agent to update or create multiple files automatically, including session files, task files, and edit-history chunks, despite the document's own explicit approval requirement. In this skill context, the instructions are directly operational and could drive broad unauthorized repository changes, making the contradiction more dangerous than a purely documentary inconsistency.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The manifest description includes broad trigger phrases such as 'db workflow', 'record session work', and 'update tasks' that can match ordinary user requests across many projects. This can cause the skill to activate in contexts where the user did not specifically intend database-backed Memory Bank operations, increasing the chance of unintended command guidance around task/session state changes.

Context Leakage

High

• Category: Data Exfiltration

Content

---
name: mb-db-workflow
description: "Record and read Memory Bank state via mb-cli. Use for projects with memory-bank/database/ and a memory_bank.db. Triggers on: db workflow, record session work, regenerate memory bank, update tasks."
---

# Memory Bank DB-Native Workflow (v6.12)

• Confidence: 84% confidence
• Finding: record session

VirusTotal

VirusTotal engine telemetry is currently stale for this artifact.

Static analysis

No suspicious patterns detected.