resume_recurring_series · Streamline MCP: Risk & Policy

WHAT IT DOES

What resume_recurring_series does on Streamline MCP

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

WHY IT NEEDS A POLICY

Why resume_recurring_series needs a policy

This tool modifies existing data (the status of a recurring task series) by reactivating it. It is reversible (can be paused again), so it falls under Write rather than Destructive. While it affects task automation, the blast radius is limited to task scheduling state changes affecting the user's own productivity data, not system-critical operations or financial transactions.

From the tool's definition Tool name 'resume_recurring_series' and description 'Resume a paused recurring task series' indicate modification of task state from paused to active. This is a reversible state change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resume_recurring_series Rate-limited

resume_recurring_series 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": {
    "resume_recurring_series": {
      "limits": [
        {
          "counter": "resume_recurring_series_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 Streamline MCP, so you can run agents against it safely.

FAQ

Questions about resume_recurring_series

What does the resume_recurring_series tool do? +

Resume a paused recurring task series. It is categorised as a Write tool in the Streamline MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resume_recurring_series? +

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

What risk level is resume_recurring_series? +

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

Can I rate-limit resume_recurring_series? +

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

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

resume_recurring_series is provided by the Streamline MCP server (rostehea/streamline-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.