set_parent_project

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 40 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/set-parent-project.md

WHAT IT DOES

What set_parent_project does on Meridian

AI agents use set_parent_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
`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.
`parent_project_id`	string	—	The parent project's id. Omit or leave empty to DETACH (make the project top-level).
`parent_project_name`	string	—	The parent project's name — an alternative to parent_project_id; resolved to an id internally.

Parameters from the server's own tool schema.

RISK

Why set_parent_project is rated Medium

This tool modifies project hierarchy metadata after creation—a classic Write operation. The changes are reversible: a project can be reparented or detached multiple times. While it enforces structural invariants (preventing circular references and deep nesting), it does not delete or irreversibly destroy data, nor does it execute arbitrary code or move money.

From the tool's definition Tool description explicitly states it can "set, change, or clear a project's parent" and "retroactively nest a project under another, or to detach it," which are reversible modifications to project structure and relationships.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

set_parent_project Rate-limited

set_parent_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": {
    "set_parent_project": {
      "limits": [
        {
          "counter": "set_parent_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 set_parent_project call is checked against it from then on.

FAQ

Questions about set_parent_project

What does the set_parent_project tool do? +

[MAINTENANCE] 7acb8563 — set, change, or clear a project's parent AFTER creation (create_project only accepted parent_project_id at creation time). Use this to retroactively nest a project under another, or to detach it. Enforces the one-level-deep invariant (3b6ff466): the parent must exist and be top-level, a project can't be its own parent, and a project that already has subprojects can't become one. Omit parent (or pass empty) to DETACH — make it top-level. Returns the updated project; {error} on an invariant violation. 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 set_parent_project accept? +

set_parent_project accepts 4 parameters: project_id, project_name, parent_project_id, parent_project_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_parent_project? +

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

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

Can I rate-limit set_parent_project? +

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

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

set_parent_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 175 Meridian tools →

Across the catalogue

set-prioity on Kanban MCP Server →create_project on Stitch MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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