advance_proposal_status

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade D, 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 call advance_proposal_status to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

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 Low

Even though advance_proposal_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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 Allowed

advance_proposal_status is read-only, so it stays allowed. 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": {}
  }
}

ALLOW ONLY 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 -- 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 Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

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 Read tool with low risk. Read-only tools are generally safe to allow by default.

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 235 Meridian tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →