get_workspace_notes
[MAINTENANCE] Read-only: List workspace-level notes (newest first). Optional ?tag substring filter.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-workspace-notes.md
What get_workspace_notes does on Meridian
AI agents call get_workspace_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 |
|---|---|---|---|
tag | string | — |
Parameters from the server's own tool schema.
Why get_workspace_notes is rated Low
This tool retrieves and lists existing data without modifying, deleting, or executing any operations. It is purely informational with negligible risk if misused by an AI agent, as it only surfaces existing notes.
From the tool's definition Tool description explicitly states 'Read-only: List workspace-level notes'. The operation is a retrieval/query with no side effects, optionally filtered by tag substring.
Attacks that exploit this kind of access
The rule that runs get_workspace_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_workspace_notes, this is the rule to start with:
get_workspace_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_workspace_notes call is checked against it from then on.
Questions about get_workspace_notes
[MAINTENANCE] Read-only: List workspace-level notes (newest first). Optional ?tag substring filter. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_workspace_notes accepts 1 parameter: tag. 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_workspace_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_workspace_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_workspace_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_workspace_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_workspace_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