split_sprint_item

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/split-sprint-item.md

WHAT IT DOES

What split_sprint_item does on Meridian

AI agents use split_sprint_item 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
`titles`	array	Yes	Titles for the new items (minimum 2).
`item_id`	string	Yes	ID of the item to split.
`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 split_sprint_item is rated Medium

This tool creates new sprint items and marks the original as closed/skipped. While closing the original could seem destructive, it is a status change (skipped) rather than a hard delete, and the data is preserved with references intact. The primary action is creating new items (Write). Misuse could disrupt sprint planning but data is recoverable.

From the tool's definition Split a sprint item into multiple smaller items. The original is closed (skipped) and N new items are created with split_from referencing the original.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

split_sprint_item Rate-limited

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

FAQ

Questions about split_sprint_item

What does the split_sprint_item tool do? +

[SUPPORT] Split a sprint item into multiple smaller items. The original is closed (skipped) and N new items are created with split_from referencing the original. Returns list of new items. 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 split_sprint_item accept? +

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

How do I enforce a policy on split_sprint_item? +

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

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

Can I rate-limit split_sprint_item? +

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

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

split_sprint_item 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 →