AI agents invoke resume_loop 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.
This tool triggers re-execution of a paused or escalated process loop ('re-enter the driver'), which constitutes running/triggering an external operation. It is not simply reading or writing data, but resuming an ongoing automated workflow. Severity is medium since resuming a loop could have downstream effects depending on the workflow state, but the description is sparse, lowering confidence.
From the tool's definition Resume a paused or escalated loop — re-enter the driver
Attacks that exploit this kind of access
Resume a paused or escalated loop — re-enter the driver. 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.
Register the Scrumdo MCP server in PolicyLayer and add a rule for resume_loop: 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.
resume_loop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resume_loop 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.
Set action: deny in the PolicyLayer policy for resume_loop. 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.
resume_loop 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →