notes_save

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Medium RISK CLASS

Category Write

Parameters 73 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/notes-save.md

WHAT IT DOES

What notes_save does on Dialogbrain

AI agents use notes_save to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.

Parameter	Type	Required	Description
`key`	string	Yes	Short identifier for this note (must not start with '__' — reserved)
`scope`	string	Yes	Scope of the note. 'workspace' = shared across all agents; 'agent' = private to this agent (was 'global' pre-PR1); 'thread' = per-conversation; 'person' = per-c
`value`	string	Yes	The note content
`pinned`	boolean	—	Pin this note so it's always loaded first. Default false.
`scope_ref_id`	string	—	Reference ID — thread_id (for scope=thread) or person_id (for scope=person). Required for thread/person scope. In MCP mode (no thread context), must be passed e
`target_agent_id`	integer	—	Target notebook. In agent mode optional (defaults to your own); required from MCP. Agents cannot target other agents' notebooks. Ignored when scope='workspace'
`expires_in_hours`	integer	—	Auto-delete after N hours. Omit for permanent notes.

Parameters from the server's own tool schema.

RISK

Why notes_save is rated Medium

The tool creates or updates notes/facts in agent memory with configurable scope (workspace, agent, thread, person). This is a write operation—it modifies state reversibly.

From the tool's definition Tool description states 'Save a fact or note into the agent's memory' and 'If a note with the same key+scope exists it will be updated.' This is a create/modify operation with reversible effects.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs notes_save safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For notes_save, this is the rule to start with:

notes_save Rate-limited

notes_save 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "notes_save": {
      "limits": [
        {
          "counter": "notes_save_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every notes_save call is checked against it from then on.

FAQ

Questions about notes_save

What does the notes_save tool do? +

Save a fact or note into the agent's memory. Use scope to choose visibility: 'workspace' = visible to every agent in this workspace (use for shared facts, project conventions); 'agent' = private to this agent (use for personal working notes); 'thread' = scoped to one conversation (use for thread-specific reminders); 'person' = scoped to one contact (use for per-contact context). If a note with the same key+scope exists it will be updated. Do NOT use this tool for behavioral rules or corrections — use feedback.save for those. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does notes_save accept? +

notes_save accepts 7 parameters: key, scope, value, pinned, scope_ref_id, target_agent_id, expires_in_hours. Required: key, scope, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on notes_save? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for notes_save: 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 Dialogbrain. Nothing to install.

What risk level is notes_save? +

notes_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit notes_save? +

Yes. Add a rate_limit block to the notes_save 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.

How do I block notes_save completely? +

Set action: deny in the PolicyLayer policy for notes_save. 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.

What MCP server provides notes_save? +

notes_save is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 224 Dialogbrain tools →

Across the catalogue

save_snapshot on Why Did You Render →notes_create on Apple Apps MCP →save_tags on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →