Skip to main content
Glama
Octonove

crbro-memory

by Octonove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Audit for credentials

crbro_audit
Read-onlyIdempotent

Scans all memory fields and session logs for stored credentials like API keys, tokens, and passwords, reporting location and type without exposing values.

Instructions

Read-only scan of every field of every neuron (facts, decisions, patterns, preferences, errors, debts, system map) and of every session log for credentials stored before the filter caught them — API keys, tokens, passwords. Reports where they sit and what kind, never the values. Findings are in the search index too, so recall can return them: remove with crbro_forget (facts for entries, session for a day log), then rotate the credential. Run it after upgrading and whenever a secret may have been pasted into a conversation. crbro_inspect shows content; this only judges it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
messageYes
findingsYes
facts_affectedYes
neurons_affectedYes
session_findingsNo
sessions_affectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed2 schema fields changedv2.0.0
    • addedOutput schema / properties / session_findings
      Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "date": {
+        "type": "string"
+      },
+      "kinds": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "session_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "session_id",
+      "date",
+      "kinds"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / sessions_affected
      Added value: +{
+  "type": "number"
+}
  3. Addedv1.14.0

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds real value beyond that: it never returns the values, findings are exposed via the search index so recall can leak them, and it states the remediation/rotation requirement. The only gap is that it doesn't describe the finding format or scope limits (e.g., pagination), which a full 5 would.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and scope, then a single sentence on the crucial caveat (never returns values), then remediation, then trigger, then sibling boundary. Every sentence earns its place; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite zero parameters and an output schema (so return values needn't be explained), the description covers what the tool scans, the sensitive-data caveat that findings are index-visible and recallable, and the required follow-up (crbro_forget + rotate). That's exactly what an agent needs to invoke and act on it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so per the rubric the baseline is 4. The description appropriately doesn't invent parameter guidance and instead spends its words on scope and follow-up actions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: a read-only scan over every neuron field and session log for stored credentials. It enumerates the scanned surfaces (facts, decisions, patterns, preferences, errors, debts, system map) and the target (API keys, tokens, passwords), so an agent can distinguish it from siblings like crbro_inspect without further reading.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the trigger ('after upgrading and whenever a secret may have been pasted into a conversation') and gives a clear boundary against the closest sibling: 'crbro_inspect shows content; this only judges it.' It also routes the remediation path to crbro_forget, so the agent knows what to call next.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools