complete_workspace_sprint_item

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 11 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/complete-workspace-sprint-item.md

WHAT IT DOES

What complete_workspace_sprint_item does on Meridian

AI agents use complete_workspace_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
`item_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why complete_workspace_sprint_item is rated Medium

This tool creates or modifies data reversibly by updating a sprint item's completion status. While it changes persistent state, the action is reversible (the completed_at marker can be cleared or the item unmarked). The tool does not delete data irreversibly, execute arbitrary code, or move funds.

From the tool's definition Mark a workspace personal-backlog item done (stamps completed_at). Returns the updated item. Persistent-state disclosure indicates this modifies and persists data (completed_at timestamp) in a database.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

complete_workspace_sprint_item Rate-limited

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

FAQ

Questions about complete_workspace_sprint_item

What does the complete_workspace_sprint_item tool do? +

[MAINTENANCE] Mark a workspace personal-backlog item done (stamps completed_at). Returns the updated 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 complete_workspace_sprint_item accept? +

complete_workspace_sprint_item accepts 1 parameter: item_id. Required: item_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on complete_workspace_sprint_item? +

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

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

Can I rate-limit complete_workspace_sprint_item? +

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

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

complete_workspace_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

reminders_complete on Apple Apps MCP → The MCP Attack Database →

Guides

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