merge_sprint_items

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/merge-sprint-items.md

WHAT IT DOES

What merge_sprint_items does on Meridian

AI agents use merge_sprint_items 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
`item_ids`	array	Yes	IDs of items to merge (minimum 2).
`new_title`	string	Yes	Title for the merged survivor item.
`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.

RISK

Why merge_sprint_items is rated Medium

This tool modifies sprint item state persistently—merging items and closing sources are Write operations that alter data structure. The operation is reversible (individual items can be deleted per the description). Not Destructive because the operation doesn't irreversibly delete data; items are merged with source status tracked (merged_into=survivor).

From the tool's definition merge_sprint_items: Merge multiple sprint items into one. Source items are closed (skipped, merged_into=survivor). Returns the new survivor item.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

merge_sprint_items Rate-limited

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

FAQ

Questions about merge_sprint_items

What does the merge_sprint_items tool do? +

[SUPPORT] Merge multiple sprint items into one. Source items are closed (skipped, merged_into=survivor). Returns the new survivor item. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account 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 merge_sprint_items accept? +

merge_sprint_items accepts 4 parameters: item_ids, new_title, project_id, project_name. Required: item_ids, new_title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on merge_sprint_items? +

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

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

Can I rate-limit merge_sprint_items? +

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

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

merge_sprint_items 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 175 Meridian tools →

Across the catalogue

The MCP Attack Database →

Guides

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