scheduled_tasks

List scheduled tasks. Auto-selects client.

SERVERClaude C2 SOURCE0xyg3n/claude-c2

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xyg3n-claude-c2/scheduled-tasks.md

WHAT IT DOES

What scheduled_tasks does on Claude C2

AI agents call scheduled_tasks to retrieve information from Claude C2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why scheduled_tasks is rated Low

This is a Read operation as it retrieves and displays existing scheduled task configurations. However, severity is elevated to medium rather than low because scheduled tasks information can be sensitive—it may reveal system automation, maintenance routines, and potentially security-relevant automated processes.

From the tool's definition Tool name 'scheduled_tasks' and description 'List scheduled tasks' indicate a query operation that retrieves information about system scheduled tasks without modifying or executing them.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs scheduled_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scheduled_tasks, this is the rule to start with:

scheduled_tasks Allowed

scheduled_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "scheduled_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every scheduled_tasks call is checked against it from then on.

FAQ

Questions about scheduled_tasks

What does the scheduled_tasks tool do? +

List scheduled tasks. Auto-selects client. It is categorised as a Read tool in the Claude C2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scheduled_tasks? +

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

What risk level is scheduled_tasks? +

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

Can I rate-limit scheduled_tasks? +

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

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

scheduled_tasks is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude C2, and thousands of servers like it.

This server

All 94 Claude C2 tools →

Across the catalogue

list_tasks on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →