pause_recurring_series · Streamline MCP: Risk & Policy

WHAT IT DOES

What pause_recurring_series does on Streamline MCP

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

This tool modifies existing data (the recurring task's status/state) without permanently deleting it. The change is reversible since the series can be resumed, placing it in the Write category. Severity is medium because pausing a task series could disrupt a user's workflow or cause missed deadlines, but the effect is containable and can be undone.

From the tool's definition Tool pauses a recurring task series, modifying its state from active to paused. Description states 'No new occurrences will be created until resumed,' indicating a reversible state change rather than deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pause_recurring_series Rate-limited

pause_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": {
    "pause_recurring_series": {
      "limits": [
        {
          "counter": "pause_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 pause_recurring_series

What does the pause_recurring_series tool do? +

Pause a recurring task series. No new occurrences will be created until resumed. 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 pause_recurring_series? +

Register the Streamline MCP server in PolicyLayer and add a rule for pause_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 pause_recurring_series? +

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

Can I rate-limit pause_recurring_series? +

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

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

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