preview_proposal_promotion
[SUPPORT] Read-only (ce4883f3): preview what commit_proposal_promotion would do for a proposal at a given depth, WITHOUT writing anything. Depths are cumulative, shallow to deep: 'proposal' (intake/scope only) -> 'investigation' (+ raw->investigating transition) -> 'pointers' (+ pointer recording...
This record as markdown: /tools/io-github-ajc3xc-meridian/preview-proposal-promotion.md
What preview_proposal_promotion does on Meridian
AI agents call preview_proposal_promotion 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 |
|---|---|---|---|
depth | string | Yes | How far to preview promoting, cumulative over every shallower depth. |
project_id | string | — | Target project — where the sprint item would land. |
proposal_id | string | Yes | |
project_name | string | — | Project name — alternative to project_id; resolved to the id internally. |
sprint_item_title | string | — | Override title for the would-be sprint item; defaults to the proposal title. |
touches_resources | array | — | Explicit resource ids for the would-be sprint item; overrides inference. |
sprint_item_version | string | — | Sprint version for the would-be item; defaults to 'current'. |
infer_touches_resources | boolean | — | Infer touches_resources from the proposal's title/body via recent git history when touches_resources is omitted. Default true. |
Parameters from the server's own tool schema.
Why preview_proposal_promotion is rated Low
Even though preview_proposal_promotion 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
The rule that runs preview_proposal_promotion 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 preview_proposal_promotion, this is the rule to start with:
preview_proposal_promotion is read-only, so it stays allowed. 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 preview_proposal_promotion call is checked against it from then on.
Questions about preview_proposal_promotion
[SUPPORT] Read-only (ce4883f3): preview what commit_proposal_promotion would do for a proposal at a given depth, WITHOUT writing anything. Depths are cumulative, shallow to deep: 'proposal' (intake/scope only) -> 'investigation' (+ raw->investigating transition) -> 'pointers' (+ pointer recording) -> 'sprint_items' (+ promote_workspace_proposal) -> 'executable_handoff' (+ a handoff scoped to the new sprint item). Returns {proposal_id, project_id, depth, already_satisfied, contract_status, would_create, wave_preview, preview_hash, computed_at}. 'already_satisfied'=true when the proposal's current status already reaches this depth (e.g. already 'promoted' and depth='sprint_items') — no-op, nothing further to preview. Otherwise 'contract_status' reports each of the 8 proposal-to-execution contract parts as present/would_create/optional_at_commit/not_applicable; 'would_create' shows the synthetic sprint-item preview (title/version/touches_resources) once depth>='sprint_items'; 'wave_preview' shows which existing parallel-safe group the item would join or conflict with (via get_parallelizable_groups, unmodified). Pass the returned 'preview_hash' to commit_proposal_promotion — a stale hash (proposal or board changed since) is rejected rather than silently committed. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
preview_proposal_promotion accepts 8 parameters: depth, project_id, proposal_id, project_name, sprint_item_title, touches_resources, sprint_item_version, infer_touches_resources. Required: depth, 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 preview_proposal_promotion: 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.
preview_proposal_promotion is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the preview_proposal_promotion 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 preview_proposal_promotion. 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.
preview_proposal_promotion 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