New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

add_workspace_note

[MAINTENANCE] Add a workspace-level wiki note that applies across ALL projects in this workspace (onboarding, cross-cutting conventions, shared infra). Unlike add_note, it is not tied to a project and is injected at the top of every project's context block + handoff. Comma-separated tags optional...

SERVERMeridian SOURCE@meridianmcp/mcp
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/add-workspace-note.md

What add_workspace_note does on Meridian

AI agents use add_workspace_note to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.

ParameterTypeRequiredDescription
body string Yes
tags string
title string Yes

Parameters from the server's own tool schema.

Why add_workspace_note is rated Medium

This tool creates and persists data (workspace notes) that affects multiple projects and is retrievable later—a reversible Write operation. While the note is visible across all projects, it does not execute code, delete data, or move money.

From the tool's definition Tool explicitly states it will 'Add a workspace-level wiki note' and 'injected at the top of every project's context block + handoff.' The description confirms persistent state storage and visibility across projects.

Risk signalsAccepts raw HTML/template content (body) · Bulk/mass operation — affects multiple targets

Questions about add_workspace_note

What does the add_workspace_note tool do? +

[MAINTENANCE] Add a workspace-level wiki note that applies across ALL projects in this workspace (onboarding, cross-cutting conventions, shared infra). Unlike add_note, it is not tied to a project and is injected at the top of every project's context block + handoff. Comma-separated tags optional. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does add_workspace_note accept? +

add_workspace_note accepts 3 parameters: body, tags, title. Required: body, title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_workspace_note? +

Register the Meridian MCP server in PolicyLayer and add a rule for add_workspace_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.

What risk level is add_workspace_note? +

add_workspace_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_workspace_note? +

Yes. Add a rate_limit block to the add_workspace_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.

How do I block add_workspace_note completely? +

Set action: deny in the PolicyLayer policy for add_workspace_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.

What MCP server provides add_workspace_note? +

add_workspace_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meridian's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.