move_workspace_note_to_project

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What move_workspace_note_to_project does on Meridian

AI agents use move_workspace_note_to_project 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.

Parameter	Type	Required	Description
`note_id`	string	Yes	The workspace note's id, as returned by get_workspace_notes/add_workspace_note.
`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.

RISK

Why move_workspace_note_to_project is rated Medium

An AI agent can call move_workspace_note_to_project faster than any human can review: one bad instruction and it creates or modifies resources in Meridian by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_workspace_note_to_project 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 move_workspace_note_to_project, this is the rule to start with:

move_workspace_note_to_project Rate-limited

move_workspace_note_to_project stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_workspace_note_to_project": {
      "limits": [
        {
          "counter": "move_workspace_note_to_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every move_workspace_note_to_project call is checked against it from then on.

FAQ

Questions about move_workspace_note_to_project

What does the move_workspace_note_to_project tool do? +

[MAINTENANCE] Reclassify a workspace-level note (visible across ALL projects) into a single project's notes: copies title/body/tags to a new project note then removes the workspace note. Tenant-safe on the source note (scoped like every other workspace-note tool) and atomic-in-effect on the write (a concurrent move/delete of the same note is detected and compensated rather than silently duplicated). Returns the new project note, or {error} if note_id is unknown/not yours, the destination project doesn't exist, or a race already claimed the note. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata -- including task log entries, pinned decisions, sprint items, notes, handoff/goal state, and HITL queue items -- are sent to and stored in Meridian's service, in an isolated per-tenant Postgres database (Neon); self-hosted deployments keep the same categories in the configured local SQLite/Postgres database. This data is visible in the dashboard and API, and may resurface in later project context or handoffs. Notes and pinned decisions can be deleted individually; task log entries and sprint items can be deleted via the dashboard/API (not exposed as an agent-facing tool); HITL queue items and handoff state have no per-record delete. Full removal of any of this data is available via project or account deletion, 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 move_workspace_note_to_project accept? +

move_workspace_note_to_project accepts 3 parameters: note_id, project_id, project_name. Required: note_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on move_workspace_note_to_project? +

Register the Meridian MCP server in PolicyLayer and add a rule for move_workspace_note_to_project: 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 move_workspace_note_to_project? +

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

Can I rate-limit move_workspace_note_to_project? +

Yes. Add a rate_limit block to the move_workspace_note_to_project 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 move_workspace_note_to_project completely? +

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

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

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 235 Meridian tools →

Across the catalogue

move-task on Kanban MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →