Low Risk

recurring_tasks_list

List all recurring tasks (scheduled skills) for the location

Part of the Rocket Plus server.

recurring_tasks_list is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE ROCKET PLUS →

Free to start. No card required.

AI agents call recurring_tasks_list to retrieve information from Rocket Plus without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though recurring_tasks_list only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recurring_tasks_list": {}
  }
}

See the full Rocket Plus policy for all 106 tools.

Get this rule live on your own Rocket Plus server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ROCKET PLUS →

View all 106 tools →

These attack patterns abuse exactly the kind of access recurring_tasks_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so recurring_tasks_list only ever does what you allow.

SECURE ROCKET PLUS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the recurring_tasks_list tool do? +

List all recurring tasks (scheduled skills) for the location. It is categorised as a Read tool in the Rocket Plus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recurring_tasks_list? +

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

What risk level is recurring_tasks_list? +

recurring_tasks_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit recurring_tasks_list? +

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

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

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

Enforce policy on every Rocket Plus tool call.

Deterministic rules across all 106 Rocket Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.