move_card_to_iteration · Scrumdo MCP: Risk & Policy

WHAT IT DOES

What move_card_to_iteration does on Scrumdo

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

WHY IT NEEDS A POLICY

Why move_card_to_iteration needs a policy

This action creates or modifies the state of a card (reassigns it to a different sprint), which is a write operation. While reversible, moving a card between iterations can affect project planning, task dependencies, and team workflows. The severity is medium rather than high because the action is not destructive, financial, or code-execution based, and can be undone by moving the card back.

From the tool's definition The tool 'move_card_to_iteration' modifies card state by relocating it to a different iteration/sprint, which is a reversible change to project organization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_card_to_iteration Rate-limited

move_card_to_iteration 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": {
    "move_card_to_iteration": {
      "limits": [
        {
          "counter": "move_card_to_iteration_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 Scrumdo, so you can run agents against it safely.

FAQ

Questions about move_card_to_iteration

What does the move_card_to_iteration tool do? +

Move a card into an iteration (sprint). It is categorised as a Write tool in the Scrumdo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_card_to_iteration? +

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

What risk level is move_card_to_iteration? +

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

Can I rate-limit move_card_to_iteration? +

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

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

move_card_to_iteration is provided by the Scrumdo MCP server (scrumdollc/scrumdo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.