get_sprint_progress
[SUPPORT] Read-only: Return a SUMMARY of sprint items by status (pending/in_progress/done/failed) optionally filtered by version or item_group. Returns total, done, in_progress, pending, failed, percent_complete, and by_status (counts only — no per-item list; call get_sprint_items(status="pending...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-sprint-progress.md
What get_sprint_progress does on Meridian
AI agents call get_sprint_progress 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 |
|---|---|---|---|
version | string | — | Filter to a specific sprint version bucket. |
item_group | string | — | Filter to a specific item group. |
project_id | string | — | |
session_id | string | — | Optional: include board_change (items added since this session started). |
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_progress is rated Low
This tool retrieves and queries sprint progress data without any side effects. It returns summary statistics (total, done, in_progress, pending, failed, percent_complete) and counts only, with no ability to create, modify, or delete data.
From the tool's definition Tool description explicitly states 'Read-only' and describes returning a SUMMARY of sprint items by status with counts and progress metrics. No modification, deletion, or execution capabilities are mentioned.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_sprint_progress 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_progress, this is the rule to start with:
get_sprint_progress 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_progress call is checked against it from then on.
Questions about get_sprint_progress
[SUPPORT] Read-only: Return a SUMMARY of sprint items by status (pending/in_progress/done/failed) optionally filtered by version or item_group. Returns total, done, in_progress, pending, failed, percent_complete, and by_status (counts only — no per-item list; call get_sprint_items(status="pending") for the live item list). Useful to see how far through the sprint we are without listing all items. Pass session_id to also get a board_change field reporting items added since that session started (live-queue signal — call this between sprint items to pick up mid-run injections). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_sprint_progress accepts 5 parameters: version, item_group, project_id, session_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_progress: 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_progress 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_progress 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_progress. 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_progress 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