promote_proposal
Promote a workspace proposal into a real sprint item, creating the link between them. The proposal must be in 'raw' or 'investigating' state. Creates a sprint item under the given project and sets the proposal's status to 'promoted' with promoted_to_sprint_item_id pointing to the new item. a8afd8...
This record as markdown: /tools/io-github-ajc3xc-meridian/promote-proposal.md
What promote_proposal does on Meridian
AI agents use promote_proposal 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 to create the sprint item under. |
proposal_id | string | Yes | |
project_name | string | — | Project name — alternative to project_id; resolved to the id internally. |
transfer_reason | string | — | Non-empty reason for a cross-project transfer; required when allow_project_transfer=true. Recorded on the promoted event. |
sprint_item_title | string | — | Override title for the sprint item; defaults to the proposal title. |
sprint_item_version | string | — | Sprint version for the new item; defaults to 'current'. |
allow_project_transfer | boolean | — | Acknowledge promoting a project-scoped proposal into a DIFFERENT project than the one it was created under. Requires transfer_reason. Default false. |
Parameters from the server's own tool schema.
Why promote_proposal is rated Medium
An AI agent can call promote_proposal 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
The rule that runs promote_proposal 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 promote_proposal, this is the rule to start with:
promote_proposal 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 promote_proposal call is checked against it from then on.
Questions about promote_proposal
Promote a workspace proposal into a real sprint item, creating the link between them. The proposal must be in 'raw' or 'investigating' state. Creates a sprint item under the given project and sets the proposal's status to 'promoted' with promoted_to_sprint_item_id pointing to the new item. a8afd8f9 — when the proposal is project-scoped (created via add_proposal with a project_id) and this project_id differs from that, the promotion is rejected UNLESS allow_project_transfer=True is passed together with a non-empty transfer_reason (recorded on the resulting 'promoted' proposal_events row). A proposal with no project_id (created via add_workspace_proposal, or predating this column) has nothing to compare against, so this check never fires for it. Returns {proposal, sprint_item_id, sprint_item_title, project_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.
promote_proposal accepts 7 parameters: project_id, proposal_id, project_name, transfer_reason, sprint_item_title, sprint_item_version, allow_project_transfer. Required: proposal_id. 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 promote_proposal: 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.
promote_proposal 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 promote_proposal 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 promote_proposal. 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.
promote_proposal 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