reconcile_sprint_drift
[MAINTENANCE] Read-only: Cross-reference pending sprint items against recent git commits and return items that may already be done. Uses keyword matching — confidence 'high' means 3+ keywords overlap (safe to mark done), 'medium' means 1-2 (verify first). Also surfaces 'notes_blocker_drift': pend...
This record as markdown: /tools/io-github-ajc3xc-meridian/reconcile-sprint-drift.md
What reconcile_sprint_drift does on Meridian
AI agents call reconcile_sprint_drift 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 |
|---|---|---|---|
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. |
Parameters from the server's own tool schema.
Why reconcile_sprint_drift is rated Low
This tool retrieves and analyzes sprint item data by cross-referencing against git history, then presents results for human decision-making. The description emphasizes read-only status and inspection (keyword matching, confidence assessment). No data is created, modified, deleted, or executed. The tool provides information to support decision-making but does not itself apply changes.
From the tool's definition Tool description explicitly states '[MAINTENANCE] Read-only' and 'Cross-reference pending sprint items against recent git commits and return items'.
Attacks that exploit this kind of access
The rule that runs reconcile_sprint_drift 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 reconcile_sprint_drift, this is the rule to start with:
reconcile_sprint_drift 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 reconcile_sprint_drift call is checked against it from then on.
Questions about reconcile_sprint_drift
[MAINTENANCE] Read-only: Cross-reference pending sprint items against recent git commits and return items that may already be done. Uses keyword matching — confidence 'high' means 3+ keywords overlap (safe to mark done), 'medium' means 1-2 (verify first). Also surfaces 'notes_blocker_drift': pending items whose notes describe a deferral or blocker (keywords: FLAGGED, DEFERRED, BLOCKED, 'not implementable', etc.) but whose structured fields (blocker_kind, deferred_until) are both unset — these items will keep surfacing as ordinary claimable work until you call update_sprint_item with blocker_kind='manual' or deferred_until=<ISO timestamp>. Call during planning sessions to identify board drift before filing new items. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
reconcile_sprint_drift accepts 2 parameters: project_id, project_name. 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 reconcile_sprint_drift: 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.
reconcile_sprint_drift 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 reconcile_sprint_drift 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 reconcile_sprint_drift. 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.
reconcile_sprint_drift 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