read_note
[SUPPORT] Read-only: Fetch one project note's full body by its per-project slug (the slug field from get_notes). The pull half of the list→read model — get_notes returns slugs without bodies, read_note pulls a single body when you need it.
This record as markdown: /tools/io-github-ajc3xc-meridian/read-note.md
What read_note does on Meridian
AI agents call read_note to retrieve information from Meridian 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 |
|---|---|---|---|
slug | string | Yes | The note's slug (kebab-cased, unique per project) as returned by get_notes. |
project_id | string | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
Parameters from the server's own tool schema.
Why read_note is rated Low
This tool retrieves and queries existing data (a note body) with no side effects. It is purely informational/retrieval-based, fitting the Read category. The explicit 'Read-only' designation and absence of any write, execute, or destructive operations confirms low severity.
From the tool's definition Tool name explicitly includes 'read', description states 'Read-only: Fetch one project note's full body' and 'The pull half of the list→read model'. No modification, deletion, or execution described.
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 Meridian, 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 Meridian, apply this rule, and every read_note call is checked against it from then on.
Questions about read_note
[SUPPORT] Read-only: Fetch one project note's full body by its per-project slug (the slug field from get_notes). The pull half of the list→read model — get_notes returns slugs without bodies, read_note pulls a single body when you need it. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
read_note accepts 3 parameters: slug, project_id, project_name. Required: slug. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian 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 Meridian. 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 Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue