This record as markdown: /tools/com-local-mcp-local-mcp/read-note.md
What read_note does on Local
AI agents call read_note to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
note_id | string | — | |
note_name | string | — |
Parameters from the server's own tool schema.
Why read_note is rated Low
This tool retrieves note content without side effects. It is a read-only operation that queries existing data. While notes may contain sensitive information, the tool itself performs only data retrieval, making it a Read category risk. Severity is low because reading notes does not alter state or enable further harmful operations without additional tools.
From the tool's definition Tool name 'read_note' and description 'Reads the full content of a note by name or ID' explicitly indicate retrieval of data with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs read_note safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_note, this is the rule to start with:
read_note is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every read_note call is checked against it from then on.
Questions about read_note
Reads the full content of a note by name or ID. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
read_note accepts 2 parameters: note_id, note_name. The full parameter table on this page comes from the server's own tool schema.
Register the Local 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 Local. 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 Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue