relocate_sprint_item_pointer

[SUPPORT] W1-J — atomically UPDATE an existing generic pointer's targets/source_type/label IN PLACE (a single UPDATE statement), replacing the delete_sprint_item_pointer + add_sprint_item_pointer workaround the pointer CRUD previously required to 'move' or correct a stored pointer. That two-call workaround is non-atomic: an exception between the delete and the re-add permanently loses the pointer, a concurrent get_sprint_item_pointers call in that window sees ZERO pointers for the item, and the pointer's id/created_at change — breaking anything that referenced it by its stable id (a decision's evidence, an artifact-provenance link). This tool preserves id/project_id/sprint_item_id/created_at exactly and never has a window where the row is absent. At least one of targets/source_type/label is required; an omitted field keeps its CURRENT stored value (pass label explicitly — including null/empty — to change or clear it; omit the key entirely to leave it untouched). When targets IS supplied, the replacement is validated exactly like add_sprint_item_pointer BEFORE the write (same malformed-pointer errors, same target_kind/freshness/repo_root rules — see that tool's description for the full target shape) — a validation failure changes nothing; when targets is omitted, the stored targets are carried over untouched (never re-run through that same filesystem check — a stored pointer's target_kind is a normalized artifact of prior validation, not fresh input to re-verify). Cross-project safe: returns {error} when pointer_id doesn't exist in project_id, exactly like a nonexistent pointer id (never distinguishes a foreign-project pointer from a missing one). 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 Destructive tool in the Meridian MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

relocate_sprint_item_pointer accepts 6 parameters: label, targets, pointer_id, project_id, source_type, project_name. Required: pointer_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 relocate_sprint_item_pointer: 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.

relocate_sprint_item_pointer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Yes. Add a rate_limit block to the relocate_sprint_item_pointer 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 relocate_sprint_item_pointer. 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.

relocate_sprint_item_pointer 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.