add_workspace_sprint_item

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 31 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/add-workspace-sprint-item.md

WHAT IT DOES

What add_workspace_sprint_item does on Meridian

AI agents use add_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
`group`	string	—	Cross-project bucket, e.g. 'thesis'/'meridian'/'personal'.
`title`	string	Yes
`human_id`	string	—	Optional: person this item is assigned to.

Parameters from the server's own tool schema.

RISK

Why add_workspace_sprint_item is rated Medium

This tool creates and stores new data (backlog items, text, metadata) in persistent storage, which is a Write operation. Severity is medium because misuse could clutter shared workspace state and metadata exposure in hosted deployments, but the operation is reversible (items can be removed or edited). The tool does not execute arbitrary code, delete data irreversibly, or move financial resources.

From the tool's definition 'Add an item to the workspace-level personal backlog' — the tool creates new task/backlog items. The description explicitly states items are 'Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_workspace_sprint_item Rate-limited

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

FAQ

Questions about add_workspace_sprint_item

What does the add_workspace_sprint_item tool do? +

[MAINTENANCE] Add an item to the workspace-level personal backlog — a cross-project board NOT tied to any single project (track thesis + Meridian + personal goals in one view). Use the per-project add_sprint_item for project work instead. 'group' is the cross-project bucket the item lives under (e.g. 'thesis', 'meridian', 'personal'); 'human_id' assigns it to a person. New items start as 'todo'. 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 add_workspace_sprint_item accept? +

add_workspace_sprint_item accepts 3 parameters: group, title, human_id. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_workspace_sprint_item? +

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

add_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 add_workspace_sprint_item? +

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

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

add_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

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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