get_sprint_notes
[SUPPORT] Read-only: Get all ephemeral scratch-pad notes for the current session. Shown at the top of session briefs so every cold start sees active constraints. Pass note_kind='thinking' to fetch only thinking_sync scratchpad notes, or 'note' for only normal notes; omit for all.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-sprint-notes.md
What get_sprint_notes does on Meridian
AI agents call get_sprint_notes 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 |
|---|---|---|---|
note_kind | string | — | |
session_id | string | Yes |
Parameters from the server's own tool schema.
Why get_sprint_notes is rated Low
This tool only queries and retrieves session notes based on optional filters (note_kind parameter). It performs no writes, deletions, code execution, or financial operations. The read-only designation and retrieval-only semantics clearly place it in the Read category. Severity is low as it accesses session metadata with no blast radius for misuse.
From the tool's definition Tool is explicitly marked '[SUPPORT] Read-only' and retrieves 'ephemeral scratch-pad notes for the current session' with no modification or side-effects capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_sprint_notes 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 get_sprint_notes, this is the rule to start with:
get_sprint_notes 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 get_sprint_notes call is checked against it from then on.
Questions about get_sprint_notes
[SUPPORT] Read-only: Get all ephemeral scratch-pad notes for the current session. Shown at the top of session briefs so every cold start sees active constraints. Pass note_kind='thinking' to fetch only thinking_sync scratchpad notes, or 'note' for only normal notes; omit for all. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_sprint_notes accepts 2 parameters: note_kind, session_id. Required: session_id. 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 get_sprint_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 Meridian. Nothing to install.
get_sprint_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 get_sprint_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 get_sprint_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.
get_sprint_notes 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