List all notes (and folders) in the vault.
AI agents call list_notes to retrieve information from brainMD without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about notes and folder structure without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function with no side effects, fitting the Read category. Severity is low because listing notes poses minimal risk even if misused by an agent—it does not alter state or access sensitive operations.
From the tool's definition Tool name is 'list_notes' and description states 'List all notes (and folders) in the vault' — a retrieval operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access list_notes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and brainMD, and nothing reaches the server without passing your rules. This is the rule we recommend for list_notes:
{
"version": "1",
"default": "deny",
"tools": {
"list_notes": {}
}
}list_notes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all notes (and folders) in the vault. It is categorised as a Read tool in the brainMD MCP Server, which means it retrieves data without modifying state.
Register the brainMD MCP server in PolicyLayer and add a rule for list_notes: 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 brainMD. Nothing to install.
list_notes is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_notes 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 list_notes. 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.
list_notes is provided by the brainMD MCP server (mi4uu/brain.md). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from brainMD, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 brainMD tools catalogued and risk-classified — across an index of 43,000+ MCP servers.