notes_delete
Delete a note by ID from the target notebook. Same identity rules as notes.save — agents can only delete from their own notebook.
This record as markdown: /tools/io-github-saloprj-dialogbrain/notes-delete.md
What notes_delete does on Dialogbrain
AI agents call notes_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
note_id | integer | Yes | ID of the note to delete |
target_agent_id | integer | — | Target notebook. In agent mode optional (defaults to your own); required from MCP. Agents cannot target other agents' notebooks. |
Parameters from the server's own tool schema.
Why notes_delete is rated Critical
This tool permanently removes data (a note) from a notebook. Deletion is inherently destructive and cannot be undone. Although access is restricted to the agent's own notebook (mitigating blast radius), the core operation is destructive. Severity is high rather than critical because the scope is limited to an individual agent's notes rather than shared or system-wide data.
From the tool's definition Tool name 'notes_delete' and description 'Delete a note by ID' — the action is irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs notes_delete 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_delete, this is the rule to start with:
notes_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every notes_delete call is checked against it from then on.
Questions about notes_delete
Delete a note by ID from the target notebook. Same identity rules as notes.save — agents can only delete from their own notebook. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
notes_delete accepts 2 parameters: note_id, target_agent_id. Required: note_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for notes_delete: 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.
notes_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the notes_delete 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.
Set action: deny in the PolicyLayer policy for notes_delete. 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.
notes_delete 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.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue