update_loop_state · Scrumdo MCP: Risk & Policy

WHAT IT DOES

What update_loop_state does on Scrumdo

AI agents use update_loop_state 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 update_loop_state needs a policy

This tool creates or modifies data in a loop's state through a merge/patch operation. The operation is reversible (data can be updated again), making it a Write action rather than Destructive. The severity is medium because unintended state modifications could disrupt workflow logic, but the impact is confined to a single loop's state object rather than system-wide data or financial operations.

From the tool's definition Tool description states 'Merge a patch into the loop's LoopState' which indicates modification of state data. The 'append-or-set' operation confirms reversible data alteration rather than deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_loop_state Rate-limited

update_loop_state 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": {
    "update_loop_state": {
      "limits": [
        {
          "counter": "update_loop_state_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 update_loop_state

What does the update_loop_state tool do? +

Merge a patch into the loop's LoopState (append-or-set: list keys. 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 update_loop_state? +

Register the Scrumdo MCP server in PolicyLayer and add a rule for update_loop_state: 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 update_loop_state? +

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

Can I rate-limit update_loop_state? +

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

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

update_loop_state 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.