create_proposal_successor
[SUPPORT] Create a NEW, distinct proposal that is a version/successor of an existing one, linked to it by an explicit typed relation (supersedes/refines/forks/continues/duplicates/responds_to) — never by mutating the predecessor or overloading family_id/proposal_events (pinned decision 6aef812e)....
This record as markdown: /tools/io-github-ajc3xc-meridian/create-proposal-successor.md
What create_proposal_successor does on Meridian
AI agents use create_proposal_successor 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 |
|---|---|---|---|
body | string | Yes | Full description for the new successor proposal. |
tags | string | — | Optional comma-separated tags for the new proposal. |
actor | string | — | Optional actor identity recorded on the new proposal's events and on the lineage edge. |
label | string | — | Optional human-readable label stored on the lineage edge itself (not on either proposal). |
title | string | Yes | Title for the new successor proposal. |
session_id | string | — | Optional caller session id, recorded on the new proposal's 'created' event. |
proposal_id | string | Yes | The PREDECESSOR proposal's id — the new proposal's relation_type points at this one. |
relation_type | string | Yes | How the new proposal relates to its predecessor. |
idempotency_key | string | — | Optional caller-supplied key; a retried call with the same key returns the original successor instead of creating a duplicate. |
Parameters from the server's own tool schema.
Why create_proposal_successor is rated Medium
An AI agent can call create_proposal_successor 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.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs create_proposal_successor 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 create_proposal_successor, this is the rule to start with:
create_proposal_successor 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every create_proposal_successor call is checked against it from then on.
Questions about create_proposal_successor
[SUPPORT] Create a NEW, distinct proposal that is a version/successor of an existing one, linked to it by an explicit typed relation (supersedes/refines/forks/continues/duplicates/responds_to) — never by mutating the predecessor or overloading family_id/proposal_events (pinned decision 6aef812e). Inherits the predecessor's project scope (project-scoped stays project-scoped, workspace-global stays workspace-global) and family_id automatically. Idempotent: pass the same idempotency_key on a retry to get back the SAME successor rather than a second one — the underlying proposal creation AND the lineage edge are both independently idempotent. Returns {proposal, lineage, predecessor_id}. 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.
create_proposal_successor accepts 9 parameters: body, tags, actor, label, title, session_id, proposal_id, relation_type, idempotency_key. Required: body, title, proposal_id, relation_type. 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 create_proposal_successor: 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.
create_proposal_successor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_proposal_successor 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 create_proposal_successor. 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.
create_proposal_successor 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