get_sprint_items
Read-only: List sprint items for a project. Optional status filter (todo|pending|in_progress|provisional_complete|done|failed|skipped|pushed|indeterminate). Cold sessions read this to know what's still owed. By default, items sharing a parent_id (subtasks) or item_group collapse into one summary ...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-sprint-items.md
What get_sprint_items does on Meridian
AI agents call get_sprint_items 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 |
|---|---|---|---|
limit | integer | — | Page size (default 50, clamped 1..500). Passing limit or cursor switches the result to the {items, has_more, next_cursor, total_count} pagination envelope. |
cursor | integer | — | Offset cursor from a prior page's next_cursor. Passing it switches the result to the pagination envelope. |
expand | boolean | — | Default false: collapse parent_id/item_group clusters (2+ items) into one summary row each. Pass true for the full ungrouped item list (pre-9d8e858c behavior). |
status | string | — | Filter by status. |
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 get_sprint_items is rated Low
Even though get_sprint_items only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_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 get_sprint_items, this is the rule to start with:
get_sprint_items 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 get_sprint_items call is checked against it from then on.
Questions about get_sprint_items
Read-only: List sprint items for a project. Optional status filter (todo|pending|in_progress|provisional_complete|done|failed|skipped|pushed|indeterminate). Cold sessions read this to know what's still owed. By default, items sharing a parent_id (subtasks) or item_group collapse into one summary row per cluster ({collapsed, cluster_kind, item_group_or_parent, count, done, description, ids}) instead of listing every item — pass expand=true for the full ungrouped list. Pagination (W1-A): pass limit and/or cursor to get a {items, has_more, next_cursor, total_count} envelope instead of the bare list — a project with hundreds of items (e.g. a large 'done' history) can otherwise return an unbounded, single-shot response. Paginated mode filters by status only — expand (clustering) is not applied to a partial page, since collapsing a cluster split across a page boundary would be misleading. Omit both limit and cursor for the legacy full list (unchanged, expand-aware) behavior. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_sprint_items accepts 6 parameters: limit, cursor, expand, status, 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 get_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.
get_sprint_items 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue