resolve_proposal_gate

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 84 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/resolve-proposal-gate.md

WHAT IT DOES

What resolve_proposal_gate does on Meridian

AI agents use resolve_proposal_gate 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
`actor`	string	Yes	Who made this decision.
`state`	string	Yes
`gate_id`	string	Yes
`decision`	string	Yes	Free-text explanation of the decision.
`expires_at`	string	—	Optionally update the expiry; omit to leave unchanged.
`project_id`	string	—
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`reopen_policy`	string	—	Optionally update the reopen policy; omit to leave unchanged.

Parameters from the server's own tool schema.

RISK

Why resolve_proposal_gate is rated Medium

An AI agent can call resolve_proposal_gate 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

RECOMMENDED RULE

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

resolve_proposal_gate Rate-limited

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

FAQ

Questions about resolve_proposal_gate

What does the resolve_proposal_gate tool do? +

[SUPPORT] Record a human decision on a proposal gate: the lane's new state (blocked | quarantined | allowed), the free-text decision, and the actor who decided (decided_at is auto-stamped). Refuses with {error} if the gate was already decided and has not yet expired — call reopen_proposal_gate first. An expired prior decision is treated as lapsed and a fresh decision is accepted directly. 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.

What parameters does resolve_proposal_gate accept? +

resolve_proposal_gate accepts 8 parameters: actor, state, gate_id, decision, expires_at, project_id, project_name, reopen_policy. Required: actor, state, gate_id, decision. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resolve_proposal_gate? +

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

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

Can I rate-limit resolve_proposal_gate? +

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

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

resolve_proposal_gate 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

resolve_projects on ACE-MCP →resolve_circuit on 0gzk → The MCP Attack Database →

Guides

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