High Risk →

recurring_tasks_run_now

Manually trigger a recurring task to run immediately

Part of the Rocket Plus MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

rocket-plus-mcp Execute Risk 3/5

AI agents invoke recurring_tasks_run_now to trigger processes or run actions in Rocket Plus. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

recurring_tasks_run_now can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-crypto-goatz-rocket-plus-mcp.yaml
tools:
  recurring_tasks_run_now:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Rocket Plus policy for all 106 tools.

Tool Name recurring_tasks_run_now
Category Execute
Risk Level High

View all 106 tools →

Agents calling execute-class tools like recurring_tasks_run_now have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

recurring_tasks_run_now is one of the high-risk operations in Rocket Plus. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the recurring_tasks_run_now tool do? +

Manually trigger a recurring task to run immediately. It is categorised as a Execute tool in the Rocket Plus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on recurring_tasks_run_now? +

Add a rule in your Intercept YAML policy under the tools section for recurring_tasks_run_now. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rocket Plus MCP server.

What risk level is recurring_tasks_run_now? +

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

Can I rate-limit recurring_tasks_run_now? +

Yes. Add a rate_limit block to the recurring_tasks_run_now rule in your Intercept 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 recurring_tasks_run_now completely? +

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

recurring_tasks_run_now is provided by the Rocket Plus MCP server (rocket-plus-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Rocket Plus

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.