advance_proposal_status

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 22 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/advance-proposal-status.md

WHAT IT DOES

What advance_proposal_status does on Meridian

AI agents use advance_proposal_status 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
`status`	string	Yes	Target status. 'promoted' is not allowed here — use promote_proposal instead.
`proposal_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why advance_proposal_status is rated Medium

This tool modifies the state of an existing proposal by advancing it through defined lifecycle stages. It is a reversible state change (transitions can cycle back, e.g., rejected → raw) with no code execution, deletion, or financial action. The blast radius is medium since misuse could incorrectly advance or reject proposals, disrupting project coordination workflows.

From the tool's definition Transition a workspace proposal through its lifecycle. Enforced transitions: raw → investigating|rejected; investigating → promoted|rejected|raw; rejected → raw. Returns the updated proposal.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

advance_proposal_status Rate-limited

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

FAQ

Questions about advance_proposal_status

What does the advance_proposal_status tool do? +

[SUPPORT] Transition a workspace proposal through its lifecycle. Enforced transitions: raw → investigating|rejected; investigating → promoted|rejected|raw; rejected → raw. 'promoted' is a terminal status reachable only via promote_proposal (which also creates the sprint item). Returns the updated proposal. 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 advance_proposal_status accept? +

advance_proposal_status accepts 2 parameters: status, proposal_id. Required: status, proposal_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on advance_proposal_status? +

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

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

Can I rate-limit advance_proposal_status? +

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

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

advance_proposal_status 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

The MCP Attack Database →

Guides

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