Read a single note. Returns content + mtime.
AI agents call read_note 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 retrieves and queries data from a markdown vault without modifying, deleting, or executing anything. It returns existing note content and metadata (modification time). The operation is read-only with no capability for side effects, fitting the 'Read' category. Severity is low because exposure would only allow unauthorized access to note data, not modification or deletion.
From the tool's definition Tool name 'read_note' and description 'Read a single note. Returns content + mtime.' indicate retrieval-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access read_note 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 read_note:
{
"version": "1",
"default": "deny",
"tools": {
"read_note": {}
}
}read_note 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.
Read a single note. Returns content + mtime. 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 read_note: 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.
read_note 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 read_note 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 read_note. 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.
read_note 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.