start_agent_run · Scrumdo MCP: Risk & Policy

WHAT IT DOES

What start_agent_run does on Scrumdo

AI agents invoke start_agent_run to trigger actions in Scrumdo. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_agent_run needs a policy

Despite the empty description, 'start_agent_run' clearly initiates autonomous agent execution based on naming convention and server context. This is an Execute action because it triggers code/agent processes with effects determined by arguments and external conditions.

From the tool's definition Tool named 'start_agent_run' with empty description; sibling context shows this server controls ScrumDo board operations (create, modify, archive cards).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_agent_run Rate-limited

start_agent_run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_agent_run": {
      "limits": [
        {
          "counter": "start_agent_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 start_agent_run

What does the start_agent_run tool do? +

start_agent_run. It is categorised as a Execute tool in the Scrumdo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_agent_run? +

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

start_agent_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_agent_run? +

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

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

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

// THE FULL RECORD

start_agent_run is one line of Scrumdo's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →