create_or_update_sprint · MCP DevOps Plan Server MCP

WHAT IT DOES

What create_or_update_sprint does on MCP DevOps Plan Server

AI agents use create_or_update_sprint to create or update resources in MCP DevOps Plan Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP DevOps Plan Server environment.

WHY IT NEEDS A POLICY

Why create_or_update_sprint needs a policy

The tool creates or updates sprints, which are reversible data modifications. This falls squarely into the Write category—it modifies project management data but does not irreversibly delete, execute arbitrary code, or involve financial transactions.

From the tool's definition Tool name and description indicate it 'Creates a new sprint or updates an existing sprint' and 'automatically adds the sprint to the project'. These are reversible creation and modification operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_or_update_sprint Rate-limited

create_or_update_sprint 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": {
    "create_or_update_sprint": {
      "limits": [
        {
          "counter": "create_or_update_sprint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP DevOps Plan Server, so you can run agents against it safely.

FAQ

Questions about create_or_update_sprint

What does the create_or_update_sprint tool do? +

Creates a new sprint or updates an existing sprint in Plan. If sprintDbid is provided, updates the sprint; otherwise creates a new one. If projectID is provided, automatically adds the sprint to the project (atomic operation). It is categorised as a Write tool in the MCP DevOps Plan Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_or_update_sprint? +

Register the MCP DevOps Plan Server MCP server in PolicyLayer and add a rule for create_or_update_sprint: 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 MCP DevOps Plan Server. Nothing to install.

What risk level is create_or_update_sprint? +

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

Can I rate-limit create_or_update_sprint? +

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

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

create_or_update_sprint is provided by the MCP DevOps Plan Server MCP server (mrchris2000/mcp-devops-plan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.